Skip to main content
Glama

NS Pros MCP Gateway

nvd__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": "nvd__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?

With no annotations, the description carries the full behavioral burden, and it delivers the most important non-obvious trait: storage is scoped to the caller's identifier (anonymous IP, BYO key hash, or account ID). It does not disclose what happens when a key is missing, whether retrieval errors or returns empty, or what the value/list looks like.

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 action and dual mode, then use cases, then related-tool pairing. No filler and nothing redundant with the schema beyond a single clarifying clause.

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 simple read-only memory tool with a fully documented schema and no output schema, the description covers purpose, mode switching, scoping, and related tools. The remaining gap is the miss/failure and return-shape behavior, which an agent would want before calling with an uncertain key.

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 all four parameters (key/name/k/label) are already documented as aliases in the schema, including the omit-to-list behavior. The description's note about omitting the key paraphrases the schema rather than adding new meaning, 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?

The description opens with a specific verb and resource ('Retrieve a value previously saved via remember') and immediately states the second mode ('or list all saved keys'). It also names the complementary tools (remember, forget), so an agent can place this tool precisely in the memory lifecycle without opening any 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?

It gives explicit when-to-use motivation with concrete examples ('the user's target ticker, an address, prior research notes, without re-deriving it from scratch') and states the alternative actions: remember to save, forget to delete. The condition that switches modes (omit the key argument) is stated in the first sentence.

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.