Skip to main content
Glama

Plos

by io.github.pipeworx-io

Recall

recall
Read-onlyIdempotent

Retrieve a value previously saved via remember, or list all saved keys (omit the key argument). Use to look up context the agent stored earlier — the user's target ticker, an address, prior research notes — without re-deriving it from scratch. Scoped to your identifier (anonymous IP, BYO key hash, or account ID). Pair with remember to save, forget to delete.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
keyNoMemory key to retrieve (omit to list all keys)

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "key": "user_research_topic"
+  },
+  {}
+]
  2. First observed

TDQS

A4.7/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, which cover the safety profile. The description adds valuable behavioral context beyond those annotations: the subtlety of omitting the key to list all saved keys, and scoping to the user's identifier. It does not contradict annotations, and adds enough extra nuance to merit a 4.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is two sentences, front-loaded with the core action. It avoids repetition, each clause adds meaningful information (pairing with remember/forget, scoping), and no word is wasted. This is a model of concise, structured writing.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a low-complexity tool with one optional parameter and no output schema, the description is fully sufficient. It covers purpose, usage, paired tools, scoping, and listing behavior. The annotations already provide read-only and idempotency context, so nothing essential is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so baseline is 3. The description reinforces the parameter behavior ('omit the key argument' to list) and enriches semantics by providing concrete examples of key values (user's target ticker, an address, prior research notes). This goes slightly beyond the schema, which only says 'Memory key to retrieve (omit to list all keys)'.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description opens with a specific verb and resource: 'Retrieve a value previously saved via remember, or list all saved keys (omit the key argument).' It clearly distinguishes the tool from siblings by mentioning remember and forget as paired operations and providing concrete use cases (ticker, address, research notes). This is a precise, unambiguous statement of purpose.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description states when to use the tool: 'Use to look up context the agent stored earlier... without re-deriving it from scratch.' It also names the companion tools 'remember' and 'forget' for save and delete operations, and explains scoping (anonymous IP, BYO key hash, account ID). This gives explicit context and alternatives, though it does not explicitly say when NOT to use it, the context is strong enough.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Plos toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

B3.2/5.0
Disambiguation2/5

Several tools have overlapping purposes: ask_pipeworx, ask_pipeworx_beta, and ask_pipeworx_grounded are near-identical in function, while compare_entities and entity_profile both fan out across data sources. The PLOS-specific tools (article, search, recent) are distinct, but the broader set creates confusion about which entry point to use for general data questions.

Naming Consistency2/5

The naming is a mix of single-word nouns (article, recent), verb phrases (search_authored_by, validate_claim), and adjective_noun constructions (recent_changes, recent_alerts). While most multi-word names use snake_case, the lack of a consistent prefix or verb_pattern (e.g., some start with action verbs, others with data categories like polymarket_ or pipeworx_) makes the set feel inconsistent.

Tool Count2/5

At 35 tools, the server is heavily over-scoped for a PLOS journal interface—only 4 tools (article, search, search_authored_by, recent) actually relate to PLOS. The remaining 31 tools form a broad Pipeworx/Polymarket data platform, which suggests the server is trying to do far more than its name implies.

Completeness2/5

For the stated domain (PLOS), the surface is thin: basic search, fetch, recent, and author search lack advanced features like citation metrics, journal browsing, or full-text download links. Conversely, the Pipeworx tools are extensive but unrelated to PLOS, so the set is simultaneously over-complete in unrelated areas and incomplete for its apparent purpose.

Resources