Skip to main content
Glama

propose_board

Propose a complete replacement Excalidraw scene for user review without modifying the board, then instruct users to refresh and review before applying.

Instructions

Propose a complete replacement Excalidraw scene for user review; does not modify the board. Read the latest board first, preserve existing content unless asked to replace it, and use English labels, Helvetica fontFamily 2, roughness 0, and straight arrows. Supply full Excalidraw elements including version/versionNonce. Tell the user to refresh proposals and review before applying.

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": {
      "baseRevision": "<baseRevision>",
      "summary": "<summary>",
      "scene": "<scene>"
    },
    "name": "propose_board"
  }
}

Input Schema

NameRequiredDescriptionDefault
sceneYes
summaryYes
baseRevisionYes
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

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, and openWorldHint=false. The description adds important behavioral context beyond that: it does not modify the board, creates a proposal for user review, and requires the user to refresh proposals before applying. It does not explain permissions or proposal persistence details, but the key safety distinction is disclosed.

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?

The description is front-loaded with purpose, then workflow and formatting constraints, then user-facing instructions. It is dense but every sentence carries actionable information and there is no wasted wording.

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 tool with a nested scene schema, up to 2000 elements, and no output schema, the description covers purpose, workflow, styling, and element requirements well. It leaves meaningful gaps around required parameters like baseRevision and summary, which an agent must infer or inspect in the 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?

Schema description coverage is low at 25%, and the description adds scene-specific meaning by requiring full Excalidraw elements with version/versionNonce plus style conventions. However, it does not explain baseRevision or summary, both of which are required parameters, so it only partially compensates for the schema gap.

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?

The description states a specific verb and resource: 'Propose a complete replacement Excalidraw scene for user review.' It also explicitly distinguishes the action from board modification ('does not modify the board'), which separates it from siblings like apply_board_proposal and save_board.

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?

The description gives clear workflow guidance: read the latest board first, preserve existing content unless asked to replace it, and tell the user to refresh proposals and review before applying. It does not explicitly name alternatives such as apply_board_proposal, but the review-oriented context is strong.

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