Skip to main content
Glama

remember_fact

Store durable facts, preferences, or decisions in a shared memory store, deduplicating entries and tagging them by source agent for cross-agent attribution.

Instructions

Deduplicate and persist a durable fact, preference, or decision into the shared store.

Tags the entry with source_agent (or THESEUSMEM_AGENT) for cross-agent attribution.

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": {
      "content": "<content>"
    },
    "name": "remember_fact"
  }
}

Input Schema

NameRequiredDescriptionDefault
tagsNo
contentYes
categoryNogeneral
trust_scoreNo
source_agentNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

B3.2/5.0
Behavior3/5

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

With no annotations, the description carries the full burden, and it does disclose two useful behaviors: deduplication against existing entries and automatic source_agent attribution with a THESEUSMEM_AGENT fallback. However, it never says what deduplication actually does (merge, skip, overwrite) or how trust_score affects the stored entry, leaving the mutation semantics ambiguous.

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?

Two tight sentences, front-loaded with the core action and scope. There is no filler, though the second sentence is dedicated to a single parameter while more consequential ones go unmentioned.

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?

The presence of an output schema removes the need to explain return values, and the dedup/attribution notes add real context. Still, a 5-parameter write tool with zero schema coverage and no annotations needs to explain trust_score and category semantics to be safely invocable.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% across 5 parameters, so the description must compensate. It only clarifies source_agent and its default fallback; content format, tags, category, and especially trust_score are left entirely undefined, which is a meaningful gap for a memory-ranking field.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb pair ('deduplicate and persist') and resource ('durable fact, preference, or decision') and names the target ('shared store'). The write-oriented framing implicitly separates it from read siblings like get_fact and search_facts, though no sibling is named explicitly.

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?

The phrase 'durable fact, preference, or decision' gives implied criteria for what belongs here, but there is no explicit when-to-use guidance, no exclusions (e.g., transient/episodic data should go elsewhere), and no mention of prerequisites. An agent must infer routing from the resource nouns alone.

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