Kadal Deck

Get a deck's analytics

get_deck_stats

Read-onlyIdempotent

Read a deck's accumulated audience analytics, trimmed to what the workspace's plan includes; level says which tier you got. views (Free): views and distinct viewers; slides (Starter): plus time per slide and past live sessions; full (Pro, Team): plus questions, reactions, exports and share-link hits. Use it for reporting after a talk; use get_live_room for what is happening right now. Read-only. Slides are keyed "h,v" (0-based column, row).

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_stats"
  }
}

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
`level`	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?

Annotations already cover the safety profile with readOnlyHint, idempotentHint, and destructiveHint. Beyond that, the description adds meaningful behavior: results are trimmed to the workspace plan and `level` indicates which tier was returned. It also documents the slide-key format, though it does not discuss auth or rate limits.

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 action and scope, then moves to tier details and the alternative tool. Every sentence carries information: no filler, no repetition beyond the useful read-only reminder.

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?

Given the existing output schema, the description does not need to explain return values in full, but it still adds plan-tier meaning that an agent needs in order to interpret the result. It also covers the key alternative and the slide-key convention.

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 already well documented in the schema. The description adds useful output context such as `level` and slide keys, but it does not add input-parameter semantics beyond 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?

The description uses a specific verb and resource: it reads a deck's accumulated audience analytics. It explicitly distinguishes tiers via `level` and separates this historical reporting tool from `get_live_room`, which covers current activity.

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 a direct usage rule: use this for reporting after a talk, and use `get_live_room` for what is happening right now. The plan-tier breakdown further clarifies what data is available at each level.

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.