Skip to main content
Glama
CROW: LLM Wiki

CROW: LLM Wiki

Official

confirm_area

Confirms or dismisses a proposed top-level folder from the user's explicit answer: yes opens it and moves its notes; no closes the proposal without changes.

Instructions

Settle a proposal of a top-level folder with the user's answer: yes opens it and moves its notes, no dismisses it.

Call it only with the user's explicit answer to a proposal from propose_area or proposals, never to answer for the user. A yes returns the proposal and the notes moved, whose links follow them; it is refused with an error when the memory already has as many top-level folders as its limit. A no moves nothing and closes the proposal.

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": {
      "id": "<id>",
      "yes": "<yes>"
    },
    "name": "confirm_area"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesThe proposal's id
yesYestrue: open the folder and move its notes; false: dismiss the proposal

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.4

TDQS

A4.8/5.0
Behavior5/5

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

Beyond the annotations (readOnlyHint=false, destructiveHint=false), the description discloses that a yes physically moves notes whose links follow them, that the folder limit causes a refusal error, and that a no moves nothing and closes the proposal. This is exactly the mutation-side-effect and failure-mode context annotations cannot convey.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three tight sentences, front-loaded with the core action and outcome split before the usage constraint and edge cases. Dense but every clause carries operational information; only the repeated yes/no explanation of effects is mildly redundant with the schema.

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?

Given an output schema already covers return shape, the description still adds the important part (proposal plus moved notes are returned, links follow) and covers the error condition. Nothing an agent needs to invoke 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?

Schema coverage is 100%, so both parameters are already documented, but the description goes slightly beyond by tying each boolean value to concrete side effects and to the limit-based error path. The value-mapping for 'yes' largely restates the schema text, which keeps this 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?

The description names a specific verb (settle/confirm) and resource (a proposal of a top-level folder), and immediately splits the outcome by answer value: 'yes opens it and moves its notes, no dismisses it.' It also implicitly separates this from propose_area/proposals by describing it as answering a proposal rather than creating one.

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?

Explicitly states the required precondition ('Call it only with the user's explicit answer to a proposal from `propose_area` or `proposals`') and the prohibition ('never to answer for the user'). Both the when-to-use and when-not-to-use cases are spelled out, and the originating siblings are named.

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