Skip to main content
Glama

NS Pros MCP Gateway

nj-mvc__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": "nj-mvc__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.1/5.0
Behavior4/5

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

With no annotations provided, the description carries the full burden and does disclose the important trait that reads are scoped per identifier (anonymous IP, BYO key hash, or account ID), which explains why a value saved earlier may not be visible. It does not state what happens when a key is missing or whether the list mode returns values or only keys, leaving error and return behavior unspecified for an annotation-free 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 two operating modes are front-loaded in the first sentence, followed by usage, scope, and pairing, so the structure matches how an agent reads. The example list ("target ticker, an address, prior research notes") is slightly padded but still earns its place by concretizing what belongs in memory.

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 four-parameter read tool with no output schema, the description covers both modes, scope isolation, and sibling relationships, which is nearly everything an agent needs. The remaining gap is result behavior on a missing key or empty memory, which matters more here because no annotations signal safety or failure semantics.

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 description coverage is 100% and every parameter already documents itself as an alias of the key, with the list-all behavior spelled out in the schema. The description's parenthetical "(omit the key argument)" restates the schema's "omit to list all keys" without adding alias resolution or formatting detail, so this is baseline.

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 states a specific verb and resource pair ("Retrieve a value previously saved via remember") and covers the second mode ("or list all saved keys") with the exact trigger condition (omit the key argument). It also names the sibling tools it works with (remember, forget), so an agent can place it in the memory family 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 Guidelines4/5

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

Usage context is clear: look up stored context (target ticker, address, prior research notes) rather than re-deriving it, and it routes to remember for saving and forget for deleting. What's missing is an explicit when-not condition, e.g. that it cannot fetch live or external data, so the agent must still infer the boundary.

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.