Skip to main content
Glama

NS Pros MCP Gateway

nsf-awards__remember

Save data the agent will need to reuse later, across this conversation or across sessions. Use when you discover something worth carrying forward (a resolved ticker, a target address, a user preference, a research subject) so you don't have to look it up again. Stored as a key-value pair scoped by your identifier. Authenticated users get persistent memory; anonymous sessions retain memory for 24 hours. Pair with recall to retrieve later, 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": "target_ticker",
      "value": "AAPL"
    },
    "name": "nsf-awards__remember"
  }
}

Input Schema

NameRequiredDescriptionDefault
kNoAlias for key.
vNoAlias for value.
keyYesMemory key (e.g., "subject_property", "target_ticker", "user_preference"). Accepts name, k, label as aliases.
dataNoAlias for value.
nameNoAlias for key.
textNoAlias for value.
labelNoAlias for key.
valueYesValue to store (any text, findings, addresses, preferences, notes). Accepts content, text, data, v as aliases; a non-string value is stored as JSON.
contentNoAlias for value.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior5/5

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

With no annotations supplied, the description carries the full behavioral burden and does so: it discloses the storage model (key-value scoped by identifier), the persistence difference between authenticated and anonymous sessions, and the 24-hour retention window for anonymous use. Those are things an agent cannot infer from the schema and materially affect whether and how it should call the 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 core action, then when-to-use, then persistence semantics and sibling routing. Every sentence contributes new information; the parenthetical example list is the only expendable element and it is short.

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 9-parameter mutation tool with no annotations and no output schema, the description covers purpose, triggers, persistence, retention, and related tools — enough to call it correctly. It omits what happens on a duplicate key (overwrite vs. append) and whether the write returns confirmation, which an agent managing long-term memory would reasonably want.

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 description coverage is 100% and already documents the key/value aliases exhaustively, so the baseline is 3. The description adds one useful framing not in the schema — that the pair is "scoped by your identifier" — but gives no guidance on key naming conventions or collision/overwrite behavior, which is the main remaining semantic gap for a 9-parameter tool.

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?

"Save data the agent will need to reuse later, across this conversation or across sessions" states a specific verb (save) and resource (agent memory) plus the scope of persistence. The closing line names recall and forget as the complementary read/delete operations, so the agent can distinguish this write tool from its siblings without opening another 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?

"Use when you discover something worth carrying forward" is an explicit trigger, reinforced by concrete examples (resolved ticker, target address, user preference, research subject). It also routes to recall for retrieval and forget for deletion, but never states a when-not condition (e.g., don't store ephemeral or derivable data), which keeps it short of a 5.

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.