Skip to main content
Glama

NS Pros MCP Gateway

nsf-awards__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": "nsf-awards__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.3/5.0
Behavior4/5

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

With no annotations supplied, the description carries the burden and does disclose the important behavioral trait: reads are scoped per identifier (anonymous IP, BYO key hash, or account ID), so the agent knows results are not globally shared. It does not state what happens when a key is absent (null, error, empty) or any retention/size limits, which are the remaining gaps.

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?

Three sentences, front-loaded with the core action and with the alternative behaviors (save/delete) at the end. The middle sentence's example list ('target ticker, an address, prior research notes') is slightly padded but does earn its place by showing the range of stored values.

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 full schema coverage and no output schema, the definition covers purpose, scoping, and sibling pairing adequately. The only material omission is the return behavior for a nonexistent key, which matters for a memory lookup tool but is a modest gap overall.

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 aliases k, name, and label are already documented. The description adds meaning beyond that by framing the key parameter as the switch between single-value retrieval and full key listing, which helps the agent reason about which call shape to use.

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?

States a specific verb and resource: retrieve a previously saved value, or list all saved keys when the key is omitted. This is distinguishable from sibling nsf-awards__remember (save) and nsf-awards__forget (delete) 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?

Gives concrete use cases (stored context, target ticker, address, prior research notes) and explicitly routes the agent to remember for saving and forget for deleting. The omit-key-to-list mechanic is stated plainly. It stops short of saying when not to use it or how to handle missing/duplicate keys, so it is strong but not exhaustive.

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.