Skip to main content
Glama
CROW: LLM Wiki

CROW: LLM Wiki

Official

rename_area

Renames a top-level folder so its notes and incoming links update automatically. Use it when a user asks to rename an area, keeping the wiki structure consistent.

Instructions

Rename a top-level folder; its notes and the links to them follow.

Call it when the user asks to rename an area. To change what it is for, use describe_folder; to fold it into another, merge_areas. Top-level folders only. Returns the folder's new name 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": {
      "folder": "<folder>",
      "name": "<name>"
    },
    "name": "rename_area"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesIts new name
folderYesThe top-level folder, e.g. /finance

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.4

TDQS

A4.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false with destructiveHint=false, so the description's job is to explain what the write actually touches; "its notes and the links to them follow" does exactly that, telling the agent links stay intact rather than breaking. It also restates the return payload, though the output schema already covers that. Minor gap: nothing about name collisions, permissions, or what happens if the target name already exists.

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 sentences, front-loaded with the action and its side effect, then routing, then the scope restriction. No filler and no repetition of the tool name as an explanation.

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?

With annotations covering safety, a full schema, and an output schema, the description only needs to cover scope, side effects, and sibling routing — and it does all three. Nothing an agent needs in order to invoke this correctly 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 a real constraint the schema does not encode: the `folder` argument must be a top-level folder, narrowing valid inputs. It adds little for `name` beyond "new name," which the schema already states.

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 gives a specific verb and resource ("Rename a top-level folder") plus the scope (top-level only), and immediately discloses the ripple effect on notes and links. An agent can distinguish it from describe_folder, merge_areas, and create_area 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 states the triggering condition ("Call it when the user asks to rename an area") and names two explicit alternatives with the conditions that select them: describe_folder for changing purpose, merge_areas for folding one folder into another. The "top-level folders only" exclusion is spelled out rather than left to inference.

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