Podcast MCP

by calebn

Overview Schema Source Related Servers Discussions Admin

Python

Local

play_ab_tool

Extract the same audio range at two history indices and play A, a short gap, then B once to compare before/after edits.

Instructions

Extract the same range at two history indices, then play A→gap→B once.

Prefer this over history_goto → play → goto → play for before/after probes. Leaves the history cursor on after_index. Default gap is 0.4s.

Input Schema

Name	Required	Default
`source`	No	premix
`dry_run`	No
`end_sec`	No
`gap_sec`	No
`rerender`	No
`start_sec`	No
`after_index`	Yes
`before_index`	Yes
`project_path`	No

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedv0.1.1Oct 19, 2026

addedInput schema / properties / project_path / anyOf

Added value: +[
+  {
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]

addedInput schema / properties / project_path / default
```
Added value: +null
```
removedInput schema / properties / project_path / type
```
Removed value: -"string"
```

changedInput schema / required

Previous value: -[
-  "project_path",
-  "before_index",
-  "after_index"
-]New value: +[
+  "before_index",
+  "after_index"
+]

First observedv0.1.0Sep 20, 2026

TDQS

A4.1/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 burden. It usefully discloses two side effects — the history cursor is left on after_index and the default gap is 0.4s — but says nothing about permissions, reversibility, or what dry_run/rerender actually change behaviorally.

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 short lines, each earning its place: the core action first, then routing, then the state side effect and default. No filler.

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 no explanation, and the cursor/gap behavior is covered. However, for a 9-parameter mutation-and-playback tool with zero annotation and zero schema-description coverage, the dry_run, rerender, and source semantics should have been addressed.

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 coverage is 0% across 9 parameters, so the description must compensate. It clarifies the two index params and the gap default and implies a shared range (start_sec/end_sec), but leaves source, dry_run, rerender, and project_path entirely undocumented in both schema and description.

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?

States a specific verb and resource: extract one range at two history indices and play A→gap→B once. The named alternative workflow (history_goto → play → goto → play) lets an agent distinguish this tool from sibling play/history tools without opening any schema.

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?

Explicitly says 'Prefer this over history_goto → play → goto → play for before/after probes,' naming the alternative and the selecting condition. Routing guidance is unambiguous with no inference required.

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

Deploy Server