Skip to main content
Glama
Podcast MCP
by calebn

inspect_clip_bleed_tool

Inspect automatic attenuation for one clip occurrence on a track and get guarded Restore targets, so you can verify bleed treatment and safe restoration options.

Instructions

Inspect automatic attenuation on one occurrence and return guarded Restore targets.

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

Input Schema

NameRequiredDescriptionDefault
clip_idYes
track_idYes
project_pathNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.4

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are supplied, so the description bears the full disclosure burden. 'Inspect' implies a non-mutating read, but the description never explicitly states read-only behavior, whether any state changes, or what permissions the clip/track access requires. The output schema covers return shape, but behavioral traits are largely undisclosed.

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?

A single front-loaded sentence with no filler or redundant restatement of the tool name. It is efficient, though its brevity edges toward under-specification rather than true crispness.

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 three-parameter tool with zero schema description coverage and no annotations, a single sentence is insufficient. An output schema exists so return values need not be explained, but parameter meaning and the inspect-then-restore workflow are both left to inference.

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% across three parameters, and the description does not compensate: it never explains what clip_id or track_id identify, why both are needed together, or what project_path does when omitted. Only a loose hint that a clip/track pair identifies 'one occurrence' is present.

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: 'Inspect automatic attenuation on one occurrence.' The phrase 'guarded Restore targets' signals its relation to restore_clip_bleed_tool, so an agent can distinguish reading from restoring. However, 'occurrence' and 'guarded Restore targets' are unglossed jargon that leave some ambiguity about the inspected unit.

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

Usage Guidelines3/5

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

Implied workflow is clear: inspect first, and the returned 'guarded Restore targets' feed a restore step. But there is no explicit when-to-use versus restore_clip_bleed_tool or apply_bleed_suppression_tool, and no stated exclusions or prerequisites, so guidance is only inferable.

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