Skip to main content
Glama

list_board_proposals

Read-only

Lists paginated proposal metadata without scene data so you can browse board proposals, then fetch a selected scene and compare its base revision before applying changes.

Instructions

List paginated proposal metadata without scenes. Fetch a selected scene with read_board_proposal. Compare baseRevision with the saved board revision before applying.

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

Input Schema

NameRequiredDescriptionDefault
limitNo
cursorNo
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

A3.9/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, and the description adds real context beyond that: results are paginated, the payload deliberately omits scenes, and there is a version-consistency caveat (compare baseRevision with the saved board revision) before applying. It stops short of describing page-size limits, ordering, or what the cursor represents.

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 compact sentences, front-loaded with what is returned and its scope. The trailing baseRevision sentence is useful workflow advice but references a field this tool's schema never mentions, which slightly muddies an otherwise tight description.

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?

With no output schema, three parameters, and low schema coverage, the description should say more about the shape of the returned metadata and the pagination cursor. It adequately covers purpose, handoff, and the version-comparison workflow, but leaves the caller guessing about page sizing and how to continue paginating.

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 description coverage is only 33% – only workspacePath is documented inline – so the description must carry the rest, and it largely does not. "Paginated" is the sole nod to limit/cursor, with no explanation of defaults, the maximum of 100, or cursor lifetime/format.

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?

"List paginated proposal metadata without scenes" gives a specific verb (List), a specific resource (proposal metadata), and an explicit scope limit (without scenes), which cleanly separates it from read_board_proposal. An agent can tell exactly what this returns without opening the schema.

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

Usage Guidelines4/5

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

It routes the agent: use list_board_proposals for the list, then read_board_proposal for a selected scene, and compare baseRevision against the saved board revision before applying. That is clear when-to-use and alternative-selection guidance, but there is no explicit exclusion (e.g. when to prefer list_changes or another listing sibling) and no note on when the personal-storage default is inappropriate.

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