Skip to main content
Glama

NS Pros MCP Gateway

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

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

With no annotations, the description carries the full behavioral burden and does well: it discloses the storage model (key-value scoped by identifier) and, critically, a retention difference the agent could not infer — persistent memory for authenticated users versus 24-hour retention for anonymous sessions. It stops short of stating what happens when an existing key is re-saved (overwrite vs. append) or any size limits, 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.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three tightly packed sentences, front-loaded with purpose, then usage, then storage/retention, then sibling pairing. No filler and no restatement of the tool name.

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 no-annotation, no-output-schema write tool with nine loosely-aliased parameters, the description supplies purpose, triggering context, scoping, auth-dependent persistence, and companion tools. The one real gap is the write semantics on key collision (does saving the same key replace the old value?), which an agent needs to know before overwriting prior memory.

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 baseline is 3, but the description adds meaning the schema does not: that storage is a key-value pair scoped to the calling agent's identifier, which explains why the aliases exist and why keys need not be globally unique. It does not explain the alias set, but the schema already handles that fully.

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', then narrows it to a key-value pair scoped by the caller's identifier. This distinguishes it cleanly from the sibling recall (retrieve) and forget (delete) tools without needing their schemas.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

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

Gives an explicit trigger ('Use when you discover something worth carrying forward') with concrete example payloads (resolved ticker, target address, user preference, research subject) that tell the agent what qualifies as worth persisting. It also names the alternatives and their roles — recall to retrieve later, forget to delete — so the agent knows exactly when to reach for this tool instead.

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.