Skip to main content
Glama

NS Pros MCP Gateway

npi-registry__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": "npi-registry__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.1/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 full burden and does real work: it discloses that memory is partitioned per identifier and that retention differs by auth state (persistent for authenticated users, 24 hours for anonymous sessions). That is exactly the kind of context an agent needs to decide whether a fact is worth saving. It does not address overwrite behaviour when the same key is saved twice, which is the main remaining gap.

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?

Four tight sentences, front-loaded with the action, then the trigger, then storage semantics, then related tools. Every sentence contributes; the parenthetical examples and the 'so you don't have to look it up again' rationale are useful rather than filler, though the rationale could be trimmed without loss.

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 nine-parameter (mostly alias) write tool with no annotations and no output schema, the definition covers purpose, trigger, scoping, retention and companion tools. The notable omission is what happens on duplicate keys and whether the call returns confirmation — behaviours an agent would benefit from knowing before relying on memory for correctness.

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 the schema already documents key, value and their many aliases, so the description adds little parameter-level detail beyond the phrase 'key-value pair scoped by your identifier'. A baseline 3 is appropriate given the schema does the heavy lifting; the description does not need to re-enumerate aliases in prose.

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 — 'Save data the agent will need to reuse later' — and immediately adds the storage model ('key-value pair scoped by your identifier'). It also positions itself against the siblings it belongs with by naming recall for retrieval and forget for deletion, so an agent can distinguish the trio 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 a clear trigger condition ('Use when you discover something worth carrying forward') backed by four concrete examples (resolved ticker, target address, user preference, research subject). Alternatives are named with their roles. It stops short of explicit exclusions — nothing says what should not be stored (secrets, bulky blobs) — so it lands just under 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.