Skip to main content
Glama

NS Pros MCP Gateway

numverify__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": "numverify__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 behavioral burden and does much of it: it discloses authentication-dependent retention (persistent for authenticated users, 24-hour expiry for anonymous sessions) and scoping by caller identifier. It omits what happens on a duplicate key (overwrite vs. error) and whether a confirmation or stored value is returned, which matter for a mutation tool with zero annotation coverage.

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?

Front-loaded with the action and persistence scope, then the trigger condition, then the durability caveat, then sibling routing — a sensible order. One clause is slightly redundant ('so you don't have to look it up again' restates the reuse point), but overall there is little waste.

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 simple two-required-parameter memory write with no output schema and no annotations, the description covers purpose, trigger, retention, and sibling routing adequately. The remaining gap is return/overwrite semantics — an agent cannot tell whether re-saving an existing key replaces the prior value or fails, which is a real ambiguity for a memory store.

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 the schema itself documents key/value semantics, alias fields (k, v, name, label, text, data, content), and the non-string-to-JSON coercion rule. The description adds only the high-level 'stored as a key-value pair' framing plus example use cases, which is the expected baseline when the schema already does the heavy lifting.

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 ('Save') and resource ('data ... as a key-value pair scoped by your identifier'), plus the persistence model. An agent immediately knows this is a write-to-memory tool that persists across turns and sessions, not a lookup or deletion tool.

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 an explicit trigger condition ('Use when you discover something worth carrying forward') with concrete example payloads (resolved ticker, target address, user preference, research subject) and names the complementary operations ('Pair with recall to retrieve later, forget to delete'). It stops short of stating when not to use it — e.g., prohibitions on storing secrets or large blobs.

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.