Skip to main content
Glama

Save planning board

save_board

Save the user's drawing to a project workspace or personal storage using a required base revision, retaining all existing revisions for safe version history.

Instructions

Save the user's drawing with a required base revision. Existing revisions are retained.

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": {
      "expectedRevision": "<expectedRevision>",
      "scene": "<scene>"
    },
    "name": "save_board"
  }
}

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.5.1

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare a non-read-only, non-destructive, closed-world write, so the bar is lower. The description adds genuinely useful behavior beyond that ("Existing revisions are retained"), clarifying that the save is append-style and prior state survives, but it omits what happens on a revision mismatch or conflict, which is the primary failure mode for an optimistic-concurrency save.

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?

Two short sentences with no filler; the concurrency constraint and the retention behavior are both front-loaded. Nothing is wasted, though the space saved could have carried conflict-handling detail.

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?

The tool takes a nested scene object and a concurrency token with no output schema, so the description should say what a successful save returns (e.g., the new revision) and how a rejected stale revision surfaces. Retention is covered, conflict and return value are not.

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 only 33%, so the description must compensate, and it partially does by framing expectedRevision as a required base revision. It says nothing about the scene payload shape, workspacePath storage selection, or the retry semantics of a stale revision, so half the parameters remain opaque.

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 and resource: "Save the user's drawing" with a required base revision. This is clearly a write-back operation on the board, but it never distinguishes itself from siblings such as save_document or apply_board_proposal, so the agent must infer which save path applies.

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 explicit when-to-use or when-not-to-use guidance, and no mention of the sibling alternatives (apply_board_proposal, propose_board, read_board). The only usage-like content is the precondition of a required base revision, which is implied rather than stated as a rule.

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