Skip to main content
Glama
calebn

Podcast MCP

by calebn
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

set_clip_fade_tool

Set fade-in and fade-out durations for one podcast clip, capping dialogue fades to join limits and fitting each fade inside the clip.

Instructions

Set the fade-in and fade-out duration of a single clip.

Dialogue fades cap at render.join_fade_max_ms. Each fade fits in the clip, and fade-out is limited to what fade-in leaves.

Input Schema

NameRequiredDescriptionDefault
clip_idYes
fade_in_msYes
fade_out_msYes
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",
-  "clip_id",
-  "fade_in_ms",
-  "fade_out_ms"
-]New value: +[
+  "clip_id",
+  "fade_in_ms",
+  "fade_out_ms"
+]
  2. First observedv0.1.0

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 full disclosure and does add real value: dialogue fades are capped at render.join_fade_max_ms, each fade must fit inside the clip, and fade-out is bounded by what fade-in leaves. However, it does not say whether exceeding the cap errors or silently clamps, whether the operation is undoable, or what state is required.

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?

Three short sentences, front-loaded with the purpose, and each subsequent sentence carries a distinct constraint. No filler or repetition.

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?

The output schema exists, so return values need not be described. The clamping semantics are a good addition, but for an unannotated mutation tool with 0% schema coverage, the omission of clip_id/project_path meaning and any error/permission behavior leaves the definition partially 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%, so the description must compensate. It adds meaning to fade_in_ms/fade_out_ms via the cap and mutual-limit rules, but clip_id and project_path receive no explanation at all, leaving half the parameters semantically bare.

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 verb+resource: setting fade-in and fade-out duration on a single clip. This implicitly separates it from sibling join-fade tools (fade_joins_tool, crossfade_joins_tool) because it targets one clip, but 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?

No statement of when to use this versus alternatives such as recommend_fades_tool, apply_fade_recommendations_tool, or fade_joins_tool, nor any prerequisites. The only guidance is a hard constraint on fade lengths, which is behavioral rather than routing information.

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