Skip to main content
Glama

Create version from draft

create_version
Idempotent

Publish one accepted draft checkpoint as a new immutable board version. Pass the exact current visibility; saving never changes audience, so a public board (every remix) changes publicly: confirm first. Reuse operationId to recover a lost response. The board may keep rendering after the version is saved.

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": {
      "board": "<board>",
      "operationId": "<operationId>",
      "expectedCheckpointId": "<expectedCheckpointId>",
      "expectedHeadVersionId": "<expectedHeadVersionId>",
      "message": "<message>",
      "visibility": "<visibility>"
    },
    "name": "create_version"
  }
}

Input Schema

NameRequiredDescriptionDefault
boardYesYour board: handle/slug or a boardrepo.com URL.
messageYesWhat this version changes, at most 500 characters.
visibilityYesExact current board visibility; saving never changes audience.
operationIdYesClient-generated UUID. Reuse for retries of the same logical step; use a new one for a new edit or save.
expectedCheckpointIdYescheckpoint.id from get_current_work.
expectedHeadVersionIdYessavedHeadVersionId from get_current_work when stale is false.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.1/5.0
Behavior5/5

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

Beyond readOnlyHint=false and idempotentHint=true, it discloses what the annotations cannot: the resulting version is immutable, saving never changes audience, a public board's change is immediately public and warrants confirmation, operationId reuse is the recovery path for a lost response, and the board may keep rendering after the version is saved. That last point is a non-obvious eventual-consistency behavior an agent would otherwise misread as a failure.

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?

Four sentences, front-loaded with purpose, then the riskiest constraint, then retry semantics, then a rendering caveat. Every sentence carries content, though the phrase "saving never changes audience" is repeated almost verbatim in the visibility parameter description.

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

Completeness4/5

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

For a six-parameter mutation with an output schema and full annotation coverage, the description covers purpose, risk, idempotency, and post-write rendering. The one gap is concurrency: expectedCheckpointId and expectedHeadVersionId imply optimistic-locking failures, but the description never says what happens when those values are stale or how to recover.

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 100%, so all six parameters are already documented, including the operationId retry semantics and the get_current_work provenance of the two expected* IDs. The description reinforces the visibility constraint ("pass the exact current visibility") but adds no syntax or meaning beyond what the schema already states, so the baseline 3 applies.

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?

"Publish one accepted draft checkpoint as a new immutable board version" names a specific verb (publish), a specific resource (board version), and a scope constraint (one accepted checkpoint). It is clear enough to separate from restore_checkpoint or push_board, but it never explicitly distinguishes itself from create_board_release, which an agent could plausibly confuse it with.

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 states a real precondition (the draft checkpoint must be accepted) and gives a caution with an action: confirm first because a public board changes publicly. It stops short of saying when to prefer this over create_board_release or push_board, and no explicit exclusions are given.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources