Skip to main content
Glama

Agent Exchange router

Remember and recall (30 days)

memory
DestructiveIdempotent

Persistent memory for agents: pass value to store (up to 4 KB, kept 30 days), omit value to recall. Keyed by your agent name, so an agent can remember facts, results and state between runs.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "agent": "<agent>",
      "key": "<key>"
    },
    "name": "memory"
  }
}

Input Schema

NameRequiredDescriptionDefault
keyYeswhat to remember
agentYesyour agent or bot name
valueNothe fact to store; omit to recall

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?

Annotations already disclose the write/destructive/idempotent profile, and the description adds real context on top: a 4 KB value cap and a 30-day retention window, plus agent-name key scoping. It does not state what happens to an existing key when a value is re-stored, but the destructiveHint plus the clarified limits make this well above baseline.

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?

One sentence with the core capability front-loaded, followed by the mode switch and the operational constraints. The parentheticals each carry distinct information (size cap, TTL, scoping) rather than restating the title.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 3-parameter tool with no output schema, the description covers storage limits, retention, and key scoping, but says nothing about what recall actually returns (single value, error on missing key, list) or about overwrite semantics on an existing key. Those are the remaining gaps an agent would hit on first use.

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%, so all three parameters are already documented. The description reinforces the mode switch on 'value' and explains that the key namespace is partitioned by agent name, but adds no format, size, or naming-syntax detail beyond the schema. Baseline 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?

States a specific verb+resource — persistent key/value memory — and disambiguates its two modes: 'pass value to store', 'omit value to recall'. An agent knows exactly what the tool does without opening the 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?

Explicitly states the trigger condition for each mode (value present = write, value omitted = read) and gives the intended context ('remember facts, results and state between runs'). No exclusion or alternative tool is named, but none of the siblings is a memory tool, so nothing is genuinely ambiguous.

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.

Resources