Skip to main content
Glama

read_board_proposal

Read-only

Retrieve one complete stored proposal by ID for drawing review, so you can inspect its full content and scope before deciding on revisions or approval.

Instructions

Read one complete stored proposal for drawing review.

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

Input Schema

NameRequiredDescriptionDefault
idYes
workspacePathNoTrusted absolute project path from this chat; pass on every call. null selects personal storage. Omission uses only the environment default.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.5.1

TDQS

B3/5.0
Behavior3/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 adds modest context with 'complete' (full record rather than a summary) and 'stored' (persisted proposal, not a live draft), but says nothing about failure modes for a missing id or storage scoping.

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?

A single front-loaded sentence with no filler; the core operation is stated immediately. It is arguably too terse, but nothing is wasted.

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

Completeness3/5

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

For a simple two-parameter read with annotations covering the safety profile, the description is minimally sufficient. However, with no output schema, the agent gets no hint of what a 'complete proposal' returns (fields, size, sections), which is the main remaining gap.

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

Parameters2/5

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

Schema coverage is only 50%; workspacePath is documented in the schema, but id carries only format/required metadata with no explanation of what it identifies. The description mentions no parameters at all, so it fails to compensate for the coverage gap.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description gives a specific verb (Read) and a specific resource (one complete stored proposal), with 'one' implicitly contrasting against collection siblings like list_board_proposals. It does not explicitly name a sibling, but the singular/full-record framing makes the operation distinguishable.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no when-to-use guidance, no stated prerequisites, and no alternative named (e.g., list_board_proposals for enumeration, read_board for the live board, apply_board_proposal for mutation). The agent must infer the retrieval-vs-mutation boundary from the name alone.

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