Skip to main content
Glama
CROW: LLM Wiki

CROW: LLM Wiki

Official

folders

Read-only

Lists every memory area with its one-line description and direct note count so you can see how notes are organized before moving, describing, renaming, or merging areas.

Instructions

List every folder of the memory with its one-line description and how many notes it holds directly.

Call it to see how the memory is organized before move_note, describe_folder, rename_area or merge_areas, or to tell the user which areas exist; to find notes by their words, use search. No model call.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "folders"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.4

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered; the description still adds two behavioral facts the annotations do not: that counts are of notes held *directly* (not recursively) and that there is "No model call" (no inference cost/latency). It stops short of covering list-size or performance characteristics, 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.

Conciseness4/5

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

Two sentences, front-loaded with the capability before the routing guidance, with no filler. The second sentence is dense with four sibling names but each earns its place by defining when to reach for this tool.

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 zero-parameter, read-only listing tool with an output schema, nothing an agent needs is missing: the shape of results (folder, one-line description, direct note count) is stated, the routing to `search` is stated, and return-value formatting is correctly left to the output schema.

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?

The tool takes zero parameters, so the schema carries nothing an agent must interpret; per the baseline this lands at 4 only when there is nothing to compensate for. The description adds no parameter meaning because none exists, and its value lies entirely in the return-content promise rather than argument semantics.

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 ("List every folder of the memory") and immediately specifies what each row contains: a one-line description and a direct note count. It is clearly distinguishable from `search`, whose job (finding notes by words) is named in the same breath.

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 explicit when-to-use triggers (before `move_note`, `describe_folder`, `rename_area`, `merge_areas`, or when telling the user which areas exist) and an explicit when-not: use `search` to find notes by their words. The alternative and the condition that selects it are both stated.

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