Skip to main content
Glama
CROW: LLM Wiki

CROW: LLM Wiki

Official

proposals

Read-only

Lists pending new top-level folder requests with IDs, names, descriptions, and notes so you can ask the user to approve or reject each and settle them with confirm_area.

Instructions

List the open proposals of new top-level folders, each with its id, name, description and notes.

Call it to put the pending proposals to the user as a yes or a no, then settle each with confirm_area; to make a new one, use propose_area. Empty when none is open.

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": "proposals"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
resultYes

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?

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered; the description adds the useful edge case 'Empty when none is open' and the intended human-in-the-loop workflow. It stops short of saying whether the list is scoped to a workspace or capped in size, which would be the remaining behavioral gap.

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 short sentences with the what-list front-loaded and the workflow after it; every sentence carries information. The phrasing 'put the pending proposals to the user as a yes or a no' is slightly convoluted for what it means.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With zero parameters, annotations for safety, and an existing output schema, the description covers purpose, next step, creation alternative, and the empty-result case. Only scoping/ordering details are left unstated, which is minor for a read-only listing tool.

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?

The tool takes no parameters, so the baseline is 4 and there is nothing for the description to disambiguate. The mention of returned fields is a bonus, though return shape is already covered by the output 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?

Opens with a specific verb and resource ('List the open proposals of new top-level folders') and even names the fields returned (id, name, description, notes), so an agent can distinguish it from propose_area and confirm_area without opening a 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?

States the call context ('put the pending proposals to the user as a yes or a no'), names the follow-up tool (confirm_area) and the alternative for the opposite action (propose_area to make a new one), giving explicit when-to-use and which-sibling guidance.

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