Kadal Deck

Publish a builder draft

publish_draft

Publish a web-builder draft as its deck's next version (or as a new deck, for a draft started from scratch), live at once to everyone who opens it. Use it once the person has finished editing at the builder link from start_quick_edit; use rollback_deck to undo it afterwards. Needs decks:write (60 changes a minute). It never silently replaces newer work: if the deck was published since the draft's base version, nothing changes and you get ok: false, reason: "diverged" with next steps — have the person open the builder (it merges the newer version in), then call again. Also refused while the draft holds merge-conflict markers or when the plan's storage is full.

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": {
      "draft": "<draft>"
    },
    "name": "publish_draft"
  }
}

Input Schema

Name	Required	Description	Default
`draft`	Yes	The draft's id (starts with `b`), from start_quick_edit or get_deck_sync's `draft.id`; it must belong to this workspace.
`force`	No	Publish over a newer version instead of stopping at `diverged`. Only when the person explicitly says to replace it; the replaced version stays in history for rollback_deck. Default false.

Output Schema

Name	Required	Description	Default
`ok`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 25, 2026

changedInput schema / properties / draft / description

Previous value: -"The draft's id (b…)."New value: +"The draft's id (starts with `b`), from start_quick_edit or get_deck_sync's `draft.id`; it must belong to this workspace."

addedInput schema / properties / force / description

Added value: +"Publish over a newer version instead of stopping at `diverged`. Only when the person explicitly says to replace it; the replaced version stays in history for rollback_deck. Default false."

First observedOct 25, 2026

TDQS

A4.8/5.0

Behavior5/5

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

Goes well beyond annotations (destructiveHint=false, idempotentHint=false): discloses the decks:write scope, a 60/min rate limit, the divergence refusal with `ok: false, reason: "diverged"` and `next` steps, and other refusal conditions (merge-conflict markers, storage full). It also reassures that it never silently overwrites newer work and that replaced versions stay in history.

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?

Front-loads the effect and follows with usage, undo path, permissions, and failure modes in a logical order. Dense but nearly every clause carries decision-relevant information; the parenthetical rate limit could be trimmed but is useful.

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

Completeness5/5

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

For a mutation tool with an output schema already present, the description covers what an agent needs: auth, throttling, success semantics (immediate live visibility), the diverged failure contract, and recovery steps. Nothing material is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3, but the description adds real meaning about the non-force path (divergence stops the publish) which clarifies what force actually overrides. It doesn't restate the draft id format or max length, leaving that to the schema.

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?

States a specific verb and resource (publish a web-builder draft) plus its exact effect: becomes the deck's next version, or a new deck for from-scratch drafts, live immediately. That scope detail distinguishes it from the sibling publish_deck, which publishes a deck rather than a draft.

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

Usage Guidelines5/5

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

Gives explicit trigger ('once the person has finished editing at the builder link from start_quick_edit') and names the alternative for reversal (rollback_deck). It also documents when the call refuses, which is when-not guidance in practice.

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

All Kadal Deck tools Inspect

Try in Browser

Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.