Skip to main content
Glama
Podcast MCP
by calebn

kit_show_tool

Display one podcast kit with its segments in order, showing where each segment belongs and whether it already exists in the library, so producers can verify structure before editing.

Instructions

Show one kit: its segments in order, where each goes, and whether each is in the library.

Errors: kit_unknown, kit_unreadable.

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": {
      "kit_id": "<kit_id>"
    },
    "name": "kit_show_tool"
  }
}

Input Schema

NameRequiredDescriptionDefault
kit_idYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.4

TDQS

B3/5.0
Behavior3/5

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

With no annotations, the description carries the full load: it discloses the returned content shape and two documented error modes (``kit_unknown``, ``kit_unreadable``), which is genuinely useful. However, it never states that the operation is read-only, whether it touches the library or filesystem, or what permissions are needed — modest coverage for a tool with zero annotation support.

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?

Two compact sentences, front-loaded with the core purpose and followed by an explicit error list — nothing wasted. The phrase 'where each goes' is slightly vague but is resolved by the surrounding context of segments and library membership.

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

Completeness3/5

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

An output schema exists, so return values need not be explained, and errors are covered. The remaining gap is the undocumented kit_id parameter and the absence of any read-only/safety signal for a tool with no annotations — adequate but not complete.

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

Parameters2/5

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

Schema description coverage is 0% and the single required parameter (kit_id) has no description in the schema. The description only implies that 'one kit' is identified by this value; it says nothing about the identifier's format, where it comes from, or whether it must already exist (the ``kit_unknown`` error hints at existence but gives no guidance on obtaining a valid id).

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a specific verb ('Show') and a single resource ('one kit'), then enumerates what is returned: ordered segments, placement, and library membership status. This makes it distinguishable from a listing tool like kit_list_tool, though no sibling is named explicitly.

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

Usage Guidelines2/5

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

There is no when-to-use guidance, no exclusions, and no mention of alternatives such as kit_list_tool or segment_show_tool. An agent must infer that this is the single-kit lookup counterpart to a list operation purely from the phrase 'one kit'.

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

Deploy Server

Other Tools