Skip to main content
Glama

NS Pros MCP Gateway

nist-standards__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": "nist-standards__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.4/5.0
Behavior4/5

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

No annotations are provided, so the description carries the full burden, and it does disclose the important non-obvious trait: storage is scoped to the caller's identifier (anonymous IP, BYO key hash, or account ID), which tells the agent why a value may not be found. It stops short of stating what happens on a missing key or how the key list is shaped, which matters for an unannotated read tool.

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 sentences, front-loaded with the primary retrieval mode before the list variant, then usage, then scoping. Every sentence earns its place and nothing is repeated.

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 four-optional-parameter key-value lookup with no output schema, this covers purpose, mode switching, usage triggers, scoping, and companion tools. The remaining gap is return/error behavior — what a miss looks like and how keys are enumerated — which is minor but not nothing for a tool with no annotations.

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

Parameters3/5

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

Schema coverage is 100% and the schema already documents all four parameters, including that k/name/label are aliases for key and that omitting key lists everything. The description restates the omit-key behavior but adds no format, casing, or collision guidance beyond the schema, so baseline 3 applies.

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?

Specific verb and resource: "Retrieve a value previously saved via remember, or list all saved keys (omit the key argument)." It covers both operating modes in one sentence and names the sibling tools (remember, forget) it pairs with, so an agent can distinguish it from the rest of the catalog without opening the schema.

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?

Explicit when-to-use with concrete examples: target ticker, an address, prior research notes, "without re-deriving it from scratch." It also states the exact condition that switches to list mode (omit the key) and names the complementary write/delete tools, leaving nothing to 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.