Skip to main content
Glama
Podcast MCP
by calebn

crossfade_joins_tool

Add crossfades at edit joins on a podcast track, bounded by the clips, and preview changes with dry_run before applying.

Instructions

Add crossfades at edit joins on a track, bounded by the clips only; dry_run previews.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "crossfade_joins_tool"
  }
}

Input Schema

NameRequiredDescriptionDefault
dry_runNo
fade_msNo
speakerNo
track_idNo
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"
    • removedInput schema / required
      Removed value: -[
      -  "project_path"
      -]
  2. First observedv0.1.0

TDQS

C2.8/5.0
Behavior2/5

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

With no annotations, the description carries the full behavioral burden. It usefully states that crossfades are bounded by the clips and that dry_run previews, but it does not disclose whether the operation modifies project audio, whether it is reversible, what permissions are needed, or how it behaves on failure.

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?

A single tightly written sentence with the core action front-loaded and no unnecessary wording. It conveys scope and the dry_run caveat efficiently.

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 five-parameter mutation tool with no annotations and 0% schema description coverage, the description is too thin. The output schema exists, so return values need not be explained, but missing parameter semantics and behavioral details leave the agent under-informed.

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 explain the five parameters. It only clarifies dry_run as a preview and track loosely, leaving fade_ms, speaker, and project_path undocumented in both schema and description.

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 and resource: add crossfades at edit joins on a track, and clarifies the bounded-by-clips scope. It does not explicitly distinguish itself from the sibling fade_joins_tool, so an agent must infer the boundary.

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?

The only usage hint is that dry_run previews, which helps but does not explain when to use this tool rather than fade_joins_tool or when not to use it. It lacks prerequisites, side-effect conditions, and alternative guidance.

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