Skip to main content
Glama
Podcast MCP
by calebn

extract_room_tone_bed_tool

Extracts a room-tone bed from a track's own quiet stretch, giving later tighten pads, gap fills, and bleed mutes a natural noise source in one undoable step.

Instructions

Cut a room-tone bed for track_id from its own quiet stretch, in one undo step.

The bed is what later fills (tighten pads, gap fills, bleed mutes) use in place of comfort noise. A track with a recorded or assigned bed, or whose audio is unchanged since the last extraction, is left as it is. With no clean stretch the reply says why (extracted: false plus reason). Undo restores the earlier bed state. A later clear_extracted_room_tone_bed_tool lasts only until the next pipeline run with room_tone.extract_bed on, which cuts a bed for a bedless track again.

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": {
      "track_id": "<track_id>"
    },
    "name": "extract_room_tone_bed_tool"
  }
}

Input Schema

NameRequiredDescriptionDefault
track_idYes
project_pathNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.4

TDQS

A4.3/5.0
Behavior5/5

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

With no annotations at all, the description carries the full burden and does so: it discloses that this is a mutation, that it is a single undo step, that undo restores the earlier bed state, that some tracks are deliberately left untouched, and that failure is signaled as extracted: false with a reason. It also warns that a clear is not permanent under the extraction pipeline setting, which is exactly the kind of cross-run behavior an agent cannot infer.

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?

It is front-loaded with the action and every sentence adds information about idempotency, failure, undo, or pipeline interaction. The final sentence about clear_extracted_room_tone_bed_tool is slightly tangential to invoking this tool but is justified because it prevents a wrong expectation about persistence.

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

Completeness4/5

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

For a two-parameter mutation tool with no annotations, the description covers mutability, reversibility, no-op semantics, and failure reporting, and an output schema exists so return shape need not be spelled out. The only real gap is the undocumented project_path and the absence of any stated prerequisite such as an existing project context.

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 description coverage is 0%, so the description must compensate for both parameters. It gives track_id real meaning (the track whose own quiet stretch is sampled) but never mentions project_path, leaving one of two parameters with no explanation anywhere in the definition.

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?

The first sentence gives a precise verb and resource (cut a room-tone bed) scoped to a specific track and to that track's own quiet stretch, plus the atomicity ('in one undo step'). The second sentence explains what the artifact is for, which distinguishes it from siblings like fill_with_room_tone_tool and clear_extracted_room_tone_bed_tool without needing their schemas.

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?

It states the effective no-op conditions (a bed already recorded/assigned, or unchanged audio) and explains how a later clear_extracted_room_tone_bed_tool interacts with the next pipeline run when room_tone.extract_bed is on. That is strong when/when-not context, but it never says explicitly that this must precede the fill operations or what to do when extraction fails, so the alternative selection is implied rather than stated.

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