Skip to main content
Glama

memory_rebuild

DestructiveIdempotent

Rebuild observed memories by re-indexing retained task events while preserving existing corrections and disabled records; historical claims remain unverified.

Instructions

Re-index retained task events into observed memories. Existing corrections and disabled records are preserved. No historical claim becomes verified.

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": {
      "task_id": "<task_id>",
      "op_id": "<op_id>"
    },
    "name": "memory_rebuild"
  }
}

Input Schema

NameRequiredDescriptionDefault
op_idYes
task_idYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.1/5.0
Behavior3/5

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

The annotations already declare destructiveHint=true and idempotentHint=true, and the description adds real value by stating that corrections and disabled records are preserved and that no historical claim becomes verified. However, it never says what the destruction actually touches — which memories are replaced, whether the operation is scoped to one task, or whether it can be undone — leaving the destructiveHint only partly explained.

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?

Three short, front-loaded sentences with no filler: the action first, then the preservation guarantee, then the epistemic caveat. Each sentence adds a distinct piece of information.

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 idempotency/destructive profile is covered by annotations. The remaining gap is parameter explanation and operational scope for a destructive rebuild, which the description does not close.

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 carries the full burden for both required parameters, yet it names neither task_id nor op_id. An agent can guess task_id scopes the rebuild to a task, but op_id's role (presumably an idempotency key, given idempotentHint) is entirely unexplained.

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 transformation: 'Re-index retained task events into observed memories.' That is clearly distinct from the sibling memory_record (writing new memories) and memory_search/memory_get (reading), so an agent can tell what this tool does without opening the schema.

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?

The description never says when to choose this over memory_record or memory_search, nor what precondition triggers a rebuild (e.g. after event ingestion or schema changes). Usage must be inferred from the phrase 're-index', which is thin guidance in a crowded memory-tool family.

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