Skip to main content
Glama

apply_board_proposal

Applies your selected stored proposal only when its base revision is still current, preventing stale changes from being applied.

Instructions

Apply the user's selected stored proposal only if its base revision is still current.

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": "apply_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

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, and openWorldHint=false, so the safety profile is supplied. The description adds a real behavioral trait beyond them — an optimistic-concurrency guard on the base revision — but never says what gets mutated on success, whether the operation is idempotent, or how the stale-revision case surfaces to the caller.

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?

A single front-loaded sentence with zero filler; the precondition is stated compactly in the same clause as the action.

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?

There is no output schema, so the description carries the burden of return/error semantics for a mutating tool, which it only partially does — the stale-revision failure mode and the post-apply state are left unstated. What it does cover (what is applied, and the currency guard) is the most important part.

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 coverage is 50%: workspacePath is already fully documented in the schema, while id has only format/pattern constraints. The description adds that id refers to a previously stored, user-selected proposal, which gives some semantic grounding, but no detail on sourcing the id or how the revision check relates to it.

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?

States a specific verb+resource ('Apply the user's selected stored proposal') plus a qualifying condition, which separates it from siblings like propose_board (create) and read_board_proposal (read). It does not name those alternatives explicitly, so differentiation is inferred rather than stated.

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

Usage Guidelines3/5

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

'the user's selected stored proposal' implies the apply step follows listing/reading and user selection, and 'only if its base revision is still current' implies a precondition. But there is no explicit when-to-use vs. alternatives and no guidance on what to do when the revision is stale.

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