Skip to main content
Glama
Podcast MCP
by calebn

set_clips_gain_tool

Set multiple podcast clips to the same gain level in dB, with one undo step covering all changes and out-of-range values rejected so no clip is altered.

Instructions

Set several clips to the same level in dB (absolute, 0 = unity, range -60 to +12).

One undo step covers every clip. A value outside the range is refused and no clip changes.

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_ids": "<clip_ids>",
      "gain_db": "<gain_db>"
    },
    "name": "set_clips_gain_tool"
  }
}

Input Schema

NameRequiredDescriptionDefault
gain_dbYes
clip_idsYes
project_pathNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.4

TDQS

A3.5/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does well: it discloses unit semantics (absolute, 0 = unity, -60 to +12), atomicity ('one undo step covers every clip'), and validation behavior ('refused and no clip changes'). Remaining gaps are permission/authorization context and what the bulk operation does when clip IDs are invalid or duplicated.

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?

Two short sentences with the unit/range constraint front-loaded and the safety behavior (undo grouping, refusal on out-of-range) stated immediately after. No redundant wording or repetition of the tool name.

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?

An output schema exists, so return values need no explanation, and the bulk-mutation semantics are covered well. However, with 0% schema coverage the unexplained project_path parameter leaves a real gap in an otherwise complete definition for a multi-parameter mutation tool.

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% for three parameters, so the description must compensate. It clarifies gain_db thoroughly (absolute dB, unity at 0, valid range) and implies clip_ids is a list of clip identifiers all receiving the same value, but project_path is never mentioned and gains no meaning from either the schema or 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?

States a concrete verb and resource ('Set several clips to the same level in dB') plus scope ('several clips'), which implicitly separates it from the singular set_clip_gain_tool. It does not explicitly name that sibling or state a boundary, so differentiation is inferred from wording rather than declared.

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?

The phrase 'several clips' implies this is the bulk variant, but there is no explicit when-to-use/when-not guidance and no named alternative for the single-clip case. Invalid-input handling ('a value outside the range is refused') is stated, but selection guidance between the sibling gain tools is left to inference.

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