Skip to main content
Glama
calebn

Podcast MCP

by calebn
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

insert_gap_tool

Insert a custom-length silence gap at a chosen time by splitting and shifting podcast tracks, creating clean pauses for edits.

Instructions

Open pure silence on the timeline (split + shift).

Do not use to fake a beat after a tight handoff unless the user asks — prefer keeping existing room tone via suggest_handoff_cut_tool bounds.

Input Schema

NameRequiredDescriptionDefault
at_timeYes
duration_secNo
project_pathNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv0.1.1
    • 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",
-  "at_time"
-]New value: +[
+  "at_time"
+]
  2. First observedv0.1.0

TDQS

B3.3/5.0
Behavior3/5

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

No annotations are present, so the description must carry the full behavioral burden. It discloses the mechanism (split + shift) and that the inserted silence is 'pure' rather than room tone, but it omits permissions, reversibility, effect on downstream clips/transcript, and undo behavior.

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?

Two sentences, front-loaded with purpose and then a concise usage caveat. No wasted words; every sentence adds value.

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

Completeness2/5

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

For a 3-parameter mutation tool with no annotations and 0% parameter schema coverage, the description is insufficient. It does not explain the parameters or the broader side effects beyond the basic split-and-shift mechanism, leaving significant gaps for an agent to invoke it correctly.

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

Parameters1/5

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

Schema description coverage is 0% and the description mentions no parameters. The three parameters (at_time, duration_sec, project_path) are completely undocumented in the description, failing to compensate for the schema 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?

States a specific action (open pure silence on the timeline) and mechanism (split + shift), which distinguishes it from room-tone-based siblings. However, it does not explicitly differentiate itself from other gap/silence tools like shorten_gaps_tool or strip_silence_tool.

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

Usage Guidelines4/5

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

Provides a clear when-not-to-use condition (faking a beat after a tight handoff) and names the preferred alternative (suggest_handoff_cut_tool). It lacks a positive when-to-use statement, so it is not fully complete.

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