Skip to main content
Glama
Podcast MCP
by calebn

segment_show_tool

Displays a single podcast library segment with its layout, level, chapter title, clips, and version numbers to verify content and audio state.

Instructions

Show one library segment: layout, level, chapter title, clips and its version numbers.

Errors: segment_unknown (no such id), segment_hash_mismatch (its audio changed).

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": {
      "segment_id": "<segment_id>"
    },
    "name": "segment_show_tool"
  }
}

Input Schema

NameRequiredDescriptionDefault
segment_idYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.4

TDQS

B3.4/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full behavioral burden. It does disclose a genuine behavioral trait beyond structured data by enumerating failure modes (segment_unknown, segment_hash_mismatch indicating the audio changed), but it omits whether the tool is strictly read-only, whether errors are raised or returned, and what the hash-mismatch condition means given no hash parameter exists in the schema.

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 short lines: the return surface first, then a compact error list. Every phrase carries information and nothing is padded, though the terse, fragment-style phrasing leaves some terms ("layout," "level") undefined.

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 spelled out, and the error taxonomy is a plus for a simple read tool. However, the segment_hash_mismatch condition is unexplained in a schema with no hash parameter, and no guidance is given on how the agent should react to either error.

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?

There is exactly one parameter and schema description coverage is 0%, so the schema adds only a title. The description says nothing about the id's format or source, only that an unknown id yields segment_unknown; the parameter is nearly self-explanatory, so this lands at minimum-viable rather than poor.

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?

"Show one library segment" pairs a specific verb with a specific resource and scope (single segment, not a list), and the description enumerates what gets returned (layout, level, chapter title, clips, version numbers). It implicitly contrasts with segment_list_tool via "one," though it never names that sibling.

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 is only implied: "one library segment" signals single-item lookup versus a list operation, and the two named errors imply the id must reference existing audio. There is no explicit when-to-use/when-not-to-use statement and no mention of prerequisites such as where a valid segment_id is obtained.

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