Skip to main content
Glama
CROW: LLM Wiki

CROW: LLM Wiki

Official

rebuild

Destructive

Delete every note and raw copy, then re-file all documents into their original folders; requires explicit confirmation because the operation is destructive and slow.

Instructions

Delete every note and file all the documents again from the memory's raw copies, into the same folders.

Call it only when the user explicitly asks to rebuild the whole memory; to fix one note use move_note or delete_note. Destructive and slow: every note, raw copy and archived version is deleted before the documents are filed again; the folders and their descriptions stay and none is opened. Without confirm=true it refuses and changes nothing. A rebuild that stops can be run again. Returns counts of the documents filed and the errors.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "rebuild"
  }
}

Input Schema

NameRequiredDescriptionDefault
confirmNotrue to really do it: every note is deleted, then filed again

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.4

TDQS

A4.9/5.0
Behavior5/5

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

Annotations already declare destructiveHint=true and readOnlyHint=false, but the description goes well past that: it specifies what is destroyed (every note, raw copy, archived version), what survives (folders and their descriptions), that no folder is opened, that the confirm guard causes a no-op refusal, and that an interrupted rebuild is resumable. That is exactly the operational context a destructive tool needs.

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?

Five sentences, each carrying distinct information in priority order: what it does, when to use it, what it destroys, the safety gate, recoverability, and return shape. No filler or restated title.

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

Completeness5/5

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

For a single-parameter destructive operation with an output schema, the description covers purpose, alternatives, destruction scope, the confirm gate, resumability, and even return counts. Nothing an agent needs to call this safely is missing.

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

Parameters4/5

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

With one parameter at 100% schema coverage, the schema already documents `confirm` including its default. The description adds value by framing it as a hard gate ("Without confirm=true it refuses and changes nothing"), telling the agent the consequence of omitting it, not just its type.

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 opens with a concrete verb and resource ("Delete every note and file all the documents again from the memory's raw copies, into the same folders") and immediately names the narrow-scope siblings it is not (`move_note`, `delete_note`). An agent can distinguish whole-memory rebuild from single-note repair without opening any schema.

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

Usage Guidelines5/5

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

It gives an explicit trigger ("only when the user explicitly asks to rebuild the whole memory") and an explicit alternative for the narrower case ("to fix one note use `move_note` or `delete_note`"). Both the when and the when-not are stated outright, with no inference required.

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