repo-memory-mcp

by andyast

Overview Schema Source Related Servers Discussions Admin

TypeScript

Local

supersede_memory

Replace an outdated memory with a newer version and link the two records.

Instructions

Mark an old memory superseded by a newer memory and link them.

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": {
      "oldId": "<oldId>",
      "newId": "<newId>"
    },
    "name": "supersede_memory"
  }
}

Input Schema

Name	Required	Description	Default
`cwd`	No
`newId`	Yes
`oldId`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Jul 30, 2026

TDQS

C2.7/5.0

Behavior2/5

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

With no annotations, the description carries full burden but only states the basic action. It does not disclose whether the operation is reversible, what state changes occur to the old memory (e.g., status update), or any side effects on related data.

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?

The description is a single sentence that directly states the tool's purpose. It is front-loaded and efficient with no wasted words.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the absence of annotations, output schema, and parameter descriptions, this tool requires more context about preconditions, effects, and return values. The current description is too sparse for reliable agent invocation.

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%, so the description must compensate, but it only mentions 'old' and 'new' memories. It does not explain the format of 'oldId'/'newId', the role of 'cwd', or any constraints (e.g., IDs must exist).

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?

The description clearly states a specific action ('supersede') on a specific resource ('memory'), with a clear effect ('mark old memory superseded by newer'). However, it does not distinguish from siblings like 'link_memories' or 'update_memory_status' beyond the verb choice.

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

Usage Guidelines2/5

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

No guidance is provided on when to use this tool versus alternatives, nor any prerequisites (e.g., both memories must exist, old memory must be active). The agent receives no hints on context or exclusions.

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