Kadal Deck

Get a deck

get_deck

Read-onlyIdempotent

Fetch one deck's settings and shareable links (view, presenter, audience join, print, dashboard). Use it to hand someone a link or to check visibility, passcodes or showcase status before update_deck; use get_deck_stats for audience analytics, get_live_room for a talk in progress, list_versions for publish history, and get_deck_sync or get_deck_source for quick-edit state and file contents. Read-only.

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": "get_deck"
  }
}

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
`id`	Yes	The deck's id (also its live room's id).
`slug`	Yes
`urls`	Yes
`title`	Yes
`version`	Yes	The version being served.
`showcase`	Yes	The deck's place in the public showcase.
`createdAt`	Yes
`published`	Yes	Whether a version has been published and is being served.
`updatedAt`	Yes
`visibility`	Yes
`hasViewPasscode`	Yes
`hasPresenterPasscode`	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.5/5.0

Behavior4/5

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

The annotations already establish read-only, idempotent, non-destructive behavior, and the description adds useful context about what is returned: settings, visibility, passcodes, showcase status, and multiple share-link types. The closing 'Read-only' is redundant with the annotations, but the description adds enough content context beyond them.

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?

The description is front-loaded with the core purpose, followed by concrete usage guidance and sibling routing. Although the alternatives sentence is dense, every clause helps the agent choose correctly, and the trailing 'Read-only' is brief.

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 simple read tool with full schema coverage, rich annotations, and an output schema, the description provides enough purpose, use-case, and alternative-routing context. There is no material gap that would prevent correct invocation or tool selection.

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%, and the single deck parameter is fully documented in the input schema, including accepted id/slug format and failure behavior. The description does not add parameter details beyond what the schema already provides, so the baseline score of 3 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?

The description names a specific verb and resource: fetching one deck's settings and shareable links, and it enumerates the link types. It also distinguishes the tool from nearby read tools such as get_deck_stats, get_live_room, list_versions, get_deck_sync, and get_deck_source.

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?

It gives explicit use cases: handing someone a link and checking visibility, passcodes, or showcase status before update_deck. It also routes the agent to specific alternatives for audience analytics, live talks, publish history, quick-edit state, and file contents.

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.