Skip to main content
Glama
Podcast MCP
by calebn

kit_save_tool

Save an ordered show kit that maps library segments to start, end, or timed positions so you can reuse consistent podcast layouts.

Instructions

Save a show kit (podcast kit save): library segments in order, each with where it goes.

Each entry is {"segment_id", "at", "version"?, "note"?}; at is start, end or a number of seconds (read when the kit is applied), version pins a segment version (omitted = the newest when the kit is applied; not a whole number from 1 is segment_version_invalid, as on the CLI). The same name with other entries becomes the next version; the same entries are reported unchanged. Returns {status, id, version}. Errors: kit_name_invalid, kit_invalid, kit_segment_missing (names every entry whose segment is not in the library).

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": {
      "name": "<name>",
      "entries": "<entries>"
    },
    "name": "kit_save_tool"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYes
entriesYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.4

TDQS

A3.8/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does well: it discloses versioning behavior (same name with different entries becomes the next version), idempotency (identical entries reported "unchanged"), the return payload, and four named error codes including the semantic detail that kit_segment_missing names every offending entry. What it omits is whether saving under an existing name overwrites/clobbers prior versions, and any permission or auth requirements for a mutation.

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?

The purpose is front-loaded in the first clause before any payload detail, and every subsequent sentence adds real information rather than restating the name. The backtick-heavy CLI-style notation and the trailing error list are dense but not wasteful. Slight deduction for the multiline formatting that buries the return shape and errors in a run-on block.

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

Completeness4/5

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

An output schema exists, so the brief "{status, id, version}" mention is bonus rather than required, and the error enumeration covers the realistic failure modes. For a two-parameter mutation with zero annotation coverage and zero schema documentation, the remaining unknowns are what happens on name collision with a different entry set (silently versioned?) and the `name` constraints that trigger kit_name_invalid.

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

Parameters4/5

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

Schema description coverage is 0% and the entries items schema is a bare object with additionalProperties, so the description must document the payload — and it does, specifying the keys segment_id, at, version, note, the accepted `at` values (start, end, or seconds), and that a non-integer version raises segment_version_invalid. The `name` parameter gets no definition beyond context, which is the only real gap.

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 states a specific verb and resource ("Save a show kit", with the CLI equivalent "podcast kit save") and immediately names the payload shape: an ordered list of library segments, each with a placement. The phrase "read when the kit is applied" implicitly distinguishes saving from the sibling apply tool, but it never explicitly names an alternative. Still clear enough to select against kit_apply_tool without opening schemas.

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

Usage Guidelines3/5

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

Usage context is implied through the save-then-apply model ("read when the kit is applied") and through the idempotency note that identical entries are reported "unchanged". There is, however, no explicit statement of when to use this versus kit_apply_tool or kit_show_tool, and no prerequisites or exclusions. An agent must infer the save-vs-apply split.

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