Skip to main content
Glama
Ardour Ultra MCP
by Elias02345

set_region_gain

Idempotent

Adjust an audio region’s amplitude in dB nondestructively to balance levels without altering the source audio.

Instructions

Set audio-region amplitude in dB nondestructively.

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": {
      "request": "<request>"
    },
    "name": "set_region_gain"
  }
}

Input Schema

NameRequiredDescriptionDefault
requestYes

Output Schema

NameRequiredDescriptionDefault
dataNo
errorNo
successNo
warningsNo
revision_afterNo
changed_objectsNo
revision_beforeNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior3/5

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

Annotations already declare readOnly=false, idempotent=true, and destructive=false, so the description's 'nondestructively' largely reinforces structured data rather than adding new information. The description says nothing about the dry_run, confirm_delete, or expected_revision fields that appear in the schema — notable for a write tool, though not contradictory.

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?

One front-loaded sentence with zero filler, and the unit and non-destructive nature are stated up front. It is arguably under-sized for the parameters involved, but nothing is wasted.

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?

An output schema and annotations exist, so return values and safety needn't be described. However, for a mutation tool whose nested request object has 0% documented fields, the agent is left guessing about dry-run semantics and revision-conflict behavior, which is a real 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% and the single request parameter nests six undocumented fields. The description only glosses gain_db (dB) and leaves dry_run, expected_revision, confirm_delete, and the -193..24 dB range entirely unexplained, so it does not compensate for the coverage gap.

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 ('Set audio-region amplitude') plus the unit (dB), which distinguishes it from gain setters on tracks or sends. It does not name those siblings explicitly, but the resource noun is precise enough for discrimination.

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

Usage Guidelines2/5

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

No guidance on when to use this versus set_track_gain or set_send_gain, no prerequisites, and no mention of when not to use it. The only hint is 'nondestructively', which describes behavior rather than selection criteria.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.