Skip to main content
Glama

Agent memory

agent_memory
Read-onlyIdempotent

Agent memory. Persistent Cloud KV Memory & Inter-Agent Dead-Drop Blackboard: store, retrieve, list, or delete persistent JSON/text state across namespaces (op=set|get|list|delete, up to 30d TTL) with secret/PII leak protection, an Ed25519 storage receipt, and a free public read permalink (/api/memory/read/:ns/:key). Free playground: https://apexfaucet.xyz/memory/ . $0.001 per call over x402 or X-API-Key.

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": {
      "namespace": "<namespace>"
    },
    "name": "agent_memory"
  }
}

Input Schema

NameRequiredDescriptionDefault
opNoOperation: set, get, list, or delete (default get).
keyNoMemory key name (required for set, get, delete).
valueNoJSON object or string value to store when op=set (max 16KB).
paymentNosigned x402 payment payload (PAYMENT-SIGNATURE).
ttlHoursNoOptional TTL in hours (1-720, default 168 / 7 days).
namespaceYesAgent or swarm namespace (e.g. "swarm-alpha").

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.2/5.0
Behavior1/5

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

Annotations declare readOnlyHint=true, destructiveHint=false, and idempotentHint=true, yet the description advertises op=set and op=delete, which write and remove persistent state. That is a direct contradiction; although it adds useful non-schema context (PII protection, Ed25519 receipt, public read permalink, pricing/auth), the mismatch forces a score of 1.

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?

Purpose is front-loaded, and the playground/pricing sentences add invocation-relevant details. However, the first sentence is a dense run-on that packs KV, blackboard, operations, TTL, leak protection, receipts, and permalink before the reader can fully parse it; still, little is truly off-topic.

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 six-parameter tool with full schema coverage but no output schema, the description covers operations, namespace scope, TTL, auth/payment, and security features. It does not explain get/list response shapes or error behavior, and the annotation contradiction leaves the agent unsure whether mutations are safe; completeness is therefore only moderate.

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 defines the op enum, key requirement, value max 16KB, payment, ttlHours range/default, and namespace. The description repeats op values and the 30-day TTL ceiling but adds no syntax, format, or constraint beyond the schema.

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 opens with a specific noun and then enumerates concrete operations ('store, retrieve, list, or delete persistent JSON/text state across namespaces') and the op values, so an agent can identify it as persistent KV memory rather than any sibling utility. It is not merely a restatement of 'Agent memory'.

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

Usage Guidelines3/5

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

It makes the data scope ('across namespaces') and operation modes clear, but it never says when to choose this tool over another or when not to use it; no sibling memory alternative is named. Guidance is implied rather than explicit.

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