Skip to main content
Glama

NS Pros MCP Gateway

nsi-bg__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": "nsi-bg__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

A3.9/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It discloses the scoping behavior ('anonymous IP, BYO key hash, or account ID') and the two operating modes (single-value retrieval vs. key listing), which is useful. It does not explicitly state that the operation is read-only, how missing keys behave, or what errors look like, leaving notable gaps for an unannotated tool.

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

Conciseness4/5

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

The description is front-loaded with the core retrieve-or-list behavior and then layers use cases, scoping, and companion tools. It is compact and every sentence contributes, though the parenthetical and scoping clause make it slightly dense.

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 memory-recall tool with no annotations and no output schema, the description covers purpose, the list mode, scope isolation, and companion tools. It does not describe the shape of a retrieved value or a key list, but the semantics of a memory store make those largely self-evident.

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%, so the schema already documents the key/k/name/label aliases and the omit-to-list behavior. The description reinforces the omit-to-list semantics but adds no alias or format detail beyond the schema, making the baseline 3 appropriate.

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 names a specific verb and resource ('Retrieve a value previously saved via remember') and covers the list-all mode ('omit the key argument'). It clearly distinguishes itself from the sibling forget and the referenced remember tool.

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

Usage Guidelines4/5

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

It gives clear when-to-use context ('look up context the agent stored earlier, the user's target ticker, an address, prior research notes, without re-deriving it') and names alternatives (remember to save, forget to delete). It stops short of stating when not to use it, so it misses the top calibration band.

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.