Skip to main content
Glama

Remember (extract & reconcile facts)

remember

Store facts from statements and automatically reconcile changes by superseding old values, retracting removals, and capturing multiple facts while tracking source provenance.

Instructions

Store fact(s) from a statement. Reconciles automatically: a new value SUPERSEDES the old one (not appended), removals are RETRACTED, and multiple facts in one message are all captured. Optional metadata tags the facts stored in this call. source records WHO/WHAT asserted the fact (an agent id, a person, a connector) — belief provenance, and the basis for source-aware reconciliation in a shared space (see set_reconcile_policy). Examples: 'We switched from Zustand to Redux Toolkit', 'Alice is the new team lead'.

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

Input Schema

NameRequiredDescriptionDefault
textYes
run_idNo
sourceNo
user_idNodefault
agent_idNo
metadataNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.11.0

TDQS

A4.1/5.0
Behavior5/5

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

Annotations only declare it is a non-readOnly, non-idempotent, non-destructive write. The description goes well beyond that by disclosing that new values SUPERSEDE rather than append, that removals are RETRACTED, that multiple facts in one message are all captured, and that source drives belief provenance in shared spaces. That is exactly the overwrite/lifecycle information an agent needs before writing.

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 core action and the reconciliation rules in the first two sentences, then parameter notes, then concrete examples. Dense but every clause carries real information; the two examples are the only mildly optional element.

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?

With an output schema present, return values need not be described, and the annotations already cover the safety profile. The reconciliation lifecycle and provenance model are well covered; the remaining gap is the unexplained run_id/user_id/agent_id scoping parameters in a 6-parameter tool.

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 0%, so the description carries the burden. It explains the two most ambiguous fields well — `metadata` tags the facts from this call, and `source` records WHO/WHAT asserted the fact and feeds source-aware reconciliation — but run_id, user_id, and agent_id are never mentioned, so half the surface stays opaque.

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 states a specific verb+resource ('Store fact(s) from a statement') and then pins down the distinctive semantics: automatic reconciliation via supersede, retraction on removal, and multi-fact extraction. That is enough for an agent to tell this apart from update_memory or forget without opening a schema.

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?

Usage is implied by the examples ('We switched from Zustand to Redux Toolkit', 'Alice is the new team lead') and by the pointer to set_reconcile_policy for source-aware reconciliation. However, there is no explicit when-not guidance or named comparison against siblings like update_memory or forget, so the agent must infer routing.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.