Kadal Deck

List decks

list_decks

Read-onlyIdempotent

List the decks in the connected workspace, most recently changed first, each with the same settings and links get_deck returns. Use it to find a deck's id or slug before any per-deck tool, or to survey the workspace; use get_deck instead when you already know the deck. Read-only. Returns every match in one response (no paging).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_decks"
  }
}

Input Schema

Name	Required	Description	Default
`search`	No	Keep only decks whose title or slug contains this text, case-insensitive (a substring, not separate words). Omit for every deck.

Output Schema

Name	Required	Description	Default
`decks`	Yes
`workspace`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 25, 2026

changedInput schema / properties / search / description

Previous value: -"Only decks whose title or slug contains this text (case-insensitive)."New value: +"Keep only decks whose title or slug contains this text, case-insensitive (a substring, not separate words). Omit for every deck."

First observedOct 25, 2026

TDQS

A4.7/5.0

Behavior5/5

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

Beyond the annotations, it discloses ordering ('most recently changed first'), payload equivalence with get_deck, and the absence of paging ('Returns every match in one response (no paging)'). The 'Read-only' statement aligns with readOnlyHint and reinforces safety.

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?

Three tight sentences: purpose and ordering first, then usage and sibling routing, then behavioral limits. No sentence is filler; the alternative tool is introduced after the primary use case.

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-only list tool with a full output schema and complete parameter documentation, the description covers the remaining gaps an agent needs: ordering, no paging, and relationship to get_deck.

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 tool has one optional parameter, and schema description coverage is 100%, so the schema already fully documents the 'search' behavior. The description does not add parameter-specific usage details beyond the baseline provided by 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?

Starts with a specific verb and resource ('List the decks') and scopes it to 'the connected workspace, most recently changed first.' It also distinguishes the tool from get_deck by naming that sibling explicitly.

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 when-to-use guidance: find a deck's id or slug before any per-deck tool, or survey the workspace. It also gives the exclusion case: 'use get_deck instead when you already know the deck.'

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.