Skip to main content
Glama

NS Pros MCP Gateway

nvd__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": "nvd__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 meaningful work: it discloses key-value storage scoped to the caller's identifier and a retention split between authenticated (persistent) and anonymous (24 hours) sessions. The notable gap is overwrite semantics — it never says whether re-saving an existing key replaces the prior value or fails, which matters for a write 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 definition is four short sentences and front-loads the action before the motivation and mechanics. 'So you don't have to look it up again' is mildly redundant motivation, but everything else — scoping, retention, companion tools — earns its space.

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 low-complexity write tool with no output schema and no annotations, the description covers purpose, retention policy, scoping, and the recall/forget pairing, which is most of what an agent needs. The remaining omission is overwrite/conflict behavior and what the call returns, which leaves a small but real hole for a mutation tool.

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 all nine properties (including the name/k/label and value/content/text/data/v alias sets) are documented in the schema itself. The description only restates the key-value model and adds no alias, format, or size guidance beyond that, so the baseline of 3 applies.

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 uses a specific verb and resource ('Save data the agent will need to reuse later') and immediately scopes it across conversations and sessions. It names the concrete payloads (resolved ticker, target address, user preference, research subject) and explicitly positions itself against recall and forget, so an agent can tell exactly what this tool is for.

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 is clear: call it 'when you discover something worth carrying forward' rather than re-looking it up later, and it names the companion tools (recall to retrieve, forget to delete). What's missing is an explicit when-not — e.g., guidance on not storing secrets or volatile data — so the boundary case is left to inference.

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.