Skip to main content
Glama
Podcast MCP
by calebn

restore_clip_bleed_tool

Save one inspected clip-bleed restore choice and reuse the command_id for retries; changed targets require re-inspection.

Instructions

Save one inspected Restore choice. Reuse command_id when retrying the same submission.

Does not render audio or restore other occurrences. Changed targets must be inspected 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": {
      "target": "<target>"
    },
    "name": "restore_clip_bleed_tool"
  }
}

Input Schema

NameRequiredDescriptionDefault
targetYes
command_idNo
project_pathNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.4

TDQS

A3.7/5.0
Behavior4/5

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

With no annotations provided, the description carries the full burden and does useful work: it discloses idempotency guidance via command_id, scope limits ('does not render audio or restore other occurrences'), and a prerequisite for changed targets. It still does not explain permissions, reversibility, or exactly what state is saved, so it is strong but not complete.

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?

Three short sentences, front-loaded with the core action, then retry guidance, then exclusions. Every sentence adds useful operational information with no visible filler.

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 description covers workflow, exclusions, and idempotency well, and the output schema means return values need not be described. However, for a tool with a required nested target object and no schema descriptions, the missing parameter semantics leave a meaningful completeness gap.

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 only clarifies command_id for retries. It does not explain the required nested target object at all, nor does it mention project_path, so an agent cannot understand the parameters from the 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?

The description states a specific action and scope: saving one inspected Restore choice, with explicit non-goals of rendering audio or restoring other occurrences. It is clearly distinguishable from an inspection tool, though the phrase 'Restore choice' is somewhat abstract without naming clip bleed directly.

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 gives clear usage conditions: the target must have been inspected, changed targets must be inspected again, and command_id should be reused for retries of the same submission. It does not name sibling alternatives explicitly, but the workflow constraints are actionable.

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