Skip to main content
Glama
Podcast MCP
by calebn

clear_extracted_room_tone_bed_tool

Remove the extracted room-tone bed from a track in one undo step, while preserving recorded or assigned beds; undo restores the removed bed.

Instructions

Take the extracted room-tone bed off track_id, in one undo step.

Only a bed cut from the track's own audio goes; a recorded or assigned bed is never removed (cleared: false, reason: recorded_bed). Fills baked into mutes keep their own copy of the bed; fills under timing holes follow the track's bed. Undo brings the bed back. The clear 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": "clear_extracted_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, the description carries the full behavioral burden and does so: it discloses undo semantics (one undo step, undo restores the bed), the exact refusal payload for non-extracted beds, and nuanced interaction with mutes/fills (baked-in fills keep their own copy, fills under timing holes follow the track's bed). It also warns that the clear is not permanent, which is the non-obvious behavior an agent would otherwise get wrong.

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?

The action is front-loaded in the first sentence, and the remaining clauses each carry distinct behavioral information rather than filler. The undo fact appears twice ("in one undo step" and "Undo brings the bed back"), a small redundancy, but the density otherwise earns its space.

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 destructive removal tool with no annotations, the description covers reversibility, refusal cases, scope limits, and persistence, and it pre-empts return-value questions despite an output schema existing. The one real hole is project_path, whose role and defaults are left entirely to the schema.

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% across two parameters. The description identifies track_id as the target of the removal but adds no format, source, or constraints for it, and project_path is never mentioned at all, so one of the two parameters is undocumented in both structured and unstructured fields.

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 opening sentence gives a specific verb and resource ("Take the extracted room-tone bed off track_id") and narrows the scope to beds cut from the track's own audio, which implicitly separates it from the sibling extract_room_tone_bed_tool and from record/assign flows. An agent can tell exactly what is removed and what is left alone.

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 applicability condition clearly: only an extracted bed from the track's own audio is removable, and a recorded or assigned bed yields cleared: false / reason: recorded_bed. It also discloses the effective lifetime (until the next pipeline run with room_tone.extract_bed on), which tells an agent when this tool's effect matters. It does not explicitly name the counterpart tool to use when no extracted bed exists, so it falls short of full alternative routing.

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