recall-kit

memory_correct

Replace a stale memory with an updated version, keeping the old one in history so only current content is returned as current.

Instructions

Replace a stale memory. The new version supersedes the old one, which is kept in history but never returned as current.

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": {
      "id": "<id>",
      "content": "<content>",
      "source": "<source>"
    },
    "name": "memory_correct"
  }
}

Input Schema

Name	Required	Description	Default
`id`	Yes
`reason`	No
`source`	Yes
`content`	Yes

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Nov 10, 2026

TDQS

A3.5/5.0

Behavior4/5

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

With no annotations supplied, the description carries the full behavioral burden and does disclose the key non-obvious trait: the old memory is archived to history rather than destroyed, and it will never surface as current. It still omits failure behavior (unknown id), whether the correction itself can be reverted, and any permission requirements for this mutation.

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?

Two short sentences, front-loaded with the action and followed by the lifecycle consequence. Nothing is redundant and no wording is wasted.

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?

An output schema exists so return values need not be described, and the archival semantics are covered. But for an unannotated mutation with three required parameters at 0% schema coverage, the definition should say more about id/source/reason and what happens on an invalid id.

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 four parameters, so the description must compensate and largely does not. 'Replace a stale memory' and 'new version' loosely imply id and content roles, but the required 'source' parameter and the optional 'reason' are never explained, leaving an agent to guess their meaning and format.

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 and resource: 'Replace a stale memory,' and adds that the new version supersedes the old. That semantics ('kept in history but never returned as current') distinguishes it from memory_forget (removal) and memory_recall (returns current), 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?

Use is implied by 'stale memory' — correct rather than forget or re-remember when a stored memory is outdated. However there is no explicit when-to-use/when-not guidance, no mention of alternatives, and no prerequisite such as whether the target id must already exist.

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

Deploy Server