Kadal Deck

List a deck's versions

list_versions

Read-onlyIdempotent

List a deck's published versions, newest first, with who published each, how (CLI, web builder, agent or rollback), what it was based on, and which one is live. Use it to pick a number for rollback_deck or get_deck_source, or to see who changed a deck when; use get_deck_sync instead to learn whether unpublished web edits are pending. Read-only. Only versions the plan retains are listed (usage.limits.versionsKept in whoami): each publish prunes the oldest, never the live one or one a draft is based on.

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": {
      "deck": "<deck>"
    },
    "name": "list_versions"
  }
}

Input Schema

Name	Required	Description	Default
`deck`	Yes	The deck's id (starts with `d`) or its slug, as list_decks returns them; case-insensitive. A deck outside this workspace fails with “No deck …” — call list_decks.

Output Schema

Name	Required	Description	Default
`deck`	Yes
`versions`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 25, 2026

changedInput schema / properties / deck / description

Previous value: -"The deck's id (d…) or its slug, as list_decks shows them."New value: +"The deck's id (starts with `d`) or its slug, as list_decks returns them; case-insensitive. A deck outside this workspace fails with “No deck …” — call list_decks."

First observedOct 25, 2026

TDQS

A4.7/5.0

Behavior5/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive), and the description adds non-obvious behavior beyond them: results are newest-first and are silently filtered by plan retention, with each publish pruning the oldest but never the live version or a draft's base. That pruning caveat is exactly the kind of hidden behavior an agent would otherwise misread as missing data, and it points to `usage.limits.versionsKept` in whoami for the bound.

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?

Front-loaded with what is returned, then routing guidance, then the retention caveat. Every clause carries information; the parenthetical method list and the pruning rule both earn their space.

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?

With an output schema present, return values need not be spelled out, yet the description still signals what each entry carries. Ordering, retention/pruning limits, sibling routing, and the counterpart sync tool are all covered, leaving nothing an agent needs before calling it.

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?

The single `deck` parameter has 100% schema coverage, including id-vs-slug format, case-insensitivity, and the exact failure message that should trigger list_decks. The description adds nothing parameter-specific, so the baseline 3 for fully documented schemas applies.

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 ('List a deck's published versions') and enumerates what each entry contains: publisher, method (CLI, web builder, agent, rollback), base version, and which is live. It is immediately distinguishable from siblings like get_deck or get_deck_sync.

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 concrete downstream consumers ('use it to pick a number for rollback_deck or get_deck_source') and an explicit negative route: 'use get_deck_sync instead to learn whether unpublished web edits are pending.' When-to-use, when-not-to-use, and the alternative are all named.

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.