Skip to main content
Glama

Store a memory entry

remember

Store a memory entry for later retrieval. REQUIRES A KEY. This does not call any language model — it stores text in an isolated per-tenant archive. Use assemble_context to get relevant entries back.

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>",
      "text": "<text>"
    },
    "name": "remember"
  }
}

Input Schema

NameRequiredDescriptionDefault
textYes
item_idNoOptional. Same id overwrites the entry. Omit for a generated one.
ttl_daysNoOptional. After this many days, assemble_context stops selecting this entry. It is not deleted, just no longer chosen. Omit to keep it eligible indefinitely, as before this field existed.
namespaceYesGroups related memories.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already state readOnlyHint=false and destructiveHint=false; the description adds genuinely new behavior, namely that no language model is invoked and that text lands in an isolated per-tenant archive. It stops short of saying what is returned (e.g. a generated item_id) or what happens when the key is missing.

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?

Three short sentences, front-loaded with the purpose and ending with the sibling pointer. The all-caps "REQUIRES A KEY" is ambiguous — it is unclear whether "key" means the namespace field or an API credential — which slightly undercuts the otherwise tight phrasing.

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 four-parameter write tool with annotations but no output schema, the description covers purpose, isolation, and the retrieval counterpart. It leaves a real gap: item_id may be auto-generated, yet the description never says whether the generated id is returned so a later overwrite is possible.

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 75%, so baseline is 3. "REQUIRES A KEY" vaguely reinforces the required namespace/text, but the description adds no syntax, format, or naming-convention detail for namespace, item_id, or ttl_days beyond what the schema already documents.

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?

"Store a memory entry for later retrieval" gives a specific verb and resource, and the final sentence names assemble_context as the read-side counterpart, so the agent can separate this write tool from its sibling without inspecting either 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?

It supplies clear routing context by pointing at assemble_context for retrieval and warns that a key is required before calling. It does not cover failure modes or limits, but for a single-purpose store tool the when-to-use signal is adequate.

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.