Skip to main content
Glama
CROW: LLM Wiki

CROW: LLM Wiki

Official

create_area

Creates a new empty top-level folder with a one-line description so new notes are routed into the right area. Call only when the user explicitly requests a new area.

Instructions

Open a new, empty top-level folder (an area) with a one-line description of what belongs in it.

Call it only when the user asks for a new area; the memory never opens one on its own. To gather existing notes into a new area, use propose_area. New notes are routed by the description. Moves no note. Returns the folder and its description; refused with an error when the memory already has as many top-level folders as its limit.

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>"
    },
    "name": "create_area"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesThe top-level folder's name, e.g. suppliers
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.9/5.0
Behavior5/5

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

Annotations only declare it as non-read-only, non-destructive, and closed-world; the description goes materially further by disclosing that it moves no note, that routing of new notes is driven by the supplied description, that it returns the folder and its description, and that it is refused with an error when the top-level folder limit is reached.

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, each load-bearing: purpose first, then the when-to-use constraint, then the alternative, then behavioral facts (no note moves, routing, return value, limit error). No filler or restatement of the name.

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 two-required-parameter creation tool with an output schema and partial annotations, the description covers the remaining gaps an agent needs: exclusivity of the area, routing semantics, no side effects on notes, and the failure mode at the folder limit.

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 functional meaning the schema does not: the `description` parameter is not cosmetic, it actively routes where new notes land, and the folder is created 'empty' rather than populated.

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 ('Open a new, empty top-level folder (an area)') plus the required descriptive payload, and explicitly distinguishes the case it does NOT handle by naming `propose_area` as the tool for gathering existing notes into a new area.

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 positive condition ('Call it only when the user asks for a new area'), a negative constraint ('the memory never opens one on its own'), and a named alternative with the condition that selects it ('To gather existing notes ... use `propose_area`').

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