Skip to main content
Glama
CROW: LLM Wiki

CROW: LLM Wiki

Official

propose_area

Proposes a new top-level folder grouping existing notes into a user-described area for approval, so nothing moves until the user confirms.

Instructions

Propose a new top-level folder that gathers existing notes, for the user to approve.

Call it when the user describes an area for notes already in the memory; for an empty one, use create_area. Nothing moves until confirm_area settles the proposal with the user's yes or no. Returns the proposal with its id, name, description and notes.

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": {
      "name": "<name>",
      "description": "<description>",
      "notes": "<notes>"
    },
    "name": "propose_area"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesThe top-level folder's name
notesYesThe notes it would hold, by path (finance/pricing.md) or id
descriptionYesOne line: what belongs in it

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.4

TDQS

A4.5/5.0
Behavior4/5

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

Although the annotations already signal readOnlyHint=false with destructiveHint=false, the description supplies the crucial missing context: nothing actually moves until `confirm_area` settles the proposal with the user's yes or no. That deferred-mutation semantics is exactly the behavioral fact an agent needs. It stops short of covering proposal lifetime, duplicates, or what happens if the proposal is never confirmed, which keeps it off a 5.

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 purpose, then the usage condition, then the state-safety guarantee. Each sentence carries distinct information and there is no filler or repetition of name or 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?

The tool has an output schema, so the brief note that it returns the proposal with id, name, description and notes is sufficient without enumerating formats. Purpose, trigger, alternative, and the staged-approval contract are all present, leaving nothing essential missing for correct invocation.

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

Parameters3/5

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

Schema description coverage is 100%, so every parameter is already documented in the schema, establishing the baseline of 3. The description only adds the constraint that the `notes` must already exist in memory; it gives no further detail on path-vs-id forms or how names collide, so it does not meaningfully exceed the schema.

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 uses a specific verb and resource ('Propose a new top-level folder') and states the scoping constraint that distinguishes it from its siblings: it gathers notes that already exist rather than creating an empty folder. Combined with the explicit pointer to `create_area`, an agent can identify the tool's role 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 ('when the user describes an area for notes already in the memory') and an explicit exclusion with the alternative to use instead ('for an empty one, use `create_area`'). It also names the follow-up step (`confirm_area`) that resolves the proposal, so the full workflow is inferable.

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