Skip to main content
Glama

NS Pros MCP Gateway

npi-registry__recall

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.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "key": "user_research_topic"
    },
    "name": "npi-registry__recall"
  }
}

Input Schema

NameRequiredDescriptionDefault
kNoAlias for key.
keyNoMemory key to retrieve (omit to list all keys). Accepts name, k, label as aliases.
nameNoAlias for key.
labelNoAlias for key.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior4/5

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

With no annotations, the description carries the full disclosure burden and does well on scoping: it reveals that storage is partitioned by identifier (anonymous IP, BYO key hash, or account ID), which explains isolation behavior an agent cannot see elsewhere. It omits what happens when a key is absent and what the listing result looks like, leaving some behavioral gaps.

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?

Three tightly written sentences, front-loaded with the dual-mode behavior, then use cases, then scoping, then sibling pairing. No repetition of schema contents and no filler.

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

Completeness4/5

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

For a zero-required-parameter read tool with no output schema and no annotations, the description covers the two invocation modes, the scoping model, and the sibling workflow. The only omissions are the response shape for a missing key and any size or key-format limits.

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 the baseline is 3, but the description adds real meaning beyond the schema by explaining that omitting the key switches the tool from retrieval to key enumeration, a semantic the schema only hints at. The alias parameters (k, name, label) are documented in the schema and need no restatement.

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') and explicitly covers the second mode ('list all saved keys') triggered by omitting the key argument. It is immediately distinguishable from sibling memory tools like remember and forget.

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?

It states concrete use cases (user's target ticker, an address, prior research notes) with the rationale of not re-deriving context, and routes to siblings: 'Pair with remember to save, forget to delete.' The omit-key branch for listing is spelled out, so an agent knows both invocation modes without inference.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.