Skip to main content
Glama
CROW: LLM Wiki

CROW: LLM Wiki

Official

merge_areas

Destructive

Merges two top-level wiki areas by moving all notes from a source folder into a target folder and deleting the emptied source. Requires confirm=true to run, since the source folder and its description are removed.

Instructions

Move every note of one top-level folder into another, then delete the emptied folder.

Call it only when the user asked to merge two areas; for one note, use move_note. Destructive: the source folder and its description are deleted, its notes are kept in the target. Without confirm=true it refuses and changes nothing. Returns the target folder and its description.

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": {
      "source": "<source>",
      "target": "<target>"
    },
    "name": "merge_areas"
  }
}

Input Schema

NameRequiredDescriptionDefault
sourceYesThe top-level folder to empty and delete, e.g. /legal
targetYesThe top-level folder that takes its notes, e.g. /contracts
confirmNotrue when the user asked for it: the first folder is deleted

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?

Goes well beyond the destructiveHint=true annotation by specifying exactly what is destroyed (the source folder and its description), what is preserved (its notes move to the target), and the safe-by-default gate (no confirm=true means it refuses and changes nothing). This is precisely the context an agent needs before invoking a destructive merge.

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?

Four short sentences, front-loaded with the action, then the routing rule, then the destructive consequences, then the confirm gate. No sentence is redundant and nothing important is buried.

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?

Complete for a destructive merge tool: prerequisites, consequences, the guard parameter, and the return value are all covered, and the presence of an output schema means return values need no further elaboration. Nothing an agent needs to call it 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?

Schema coverage is 100%, so the baseline is 3, but the description adds meaning the schema does not: notes are kept while the source folder's description is lost, and confirm acts as a refusal gate rather than a passive flag. It does not add syntax details beyond the schema's own examples, so it stops short of a 5.

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?

States a specific verb and resource with full scope: move every note from one top-level folder into another, then delete the emptied folder. The agent can distinguish it immediately from move_note, which is named explicitly for the single-note case.

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?

Gives an explicit when-to-use condition (only when the user asked to merge two areas) and names the alternative for the near-miss case (move_note for one note). The confirm=true requirement is also stated as a usage precondition.

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