Skip to main content
Glama
Ardour Ultra MCP
by Elias02345

set_region_fades

Idempotent

Adjust a region's audio fade-in and fade-out durations in samples while keeping existing fade shapes intact.

Instructions

Set audio fade durations in samples; preserve current fade shapes.

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_fades"
  }
}

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

B3/5.0
Behavior3/5

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

Annotations already declare it is a non-read-only but non-destructive, idempotent, closed-world write. The description adds real context beyond that with 'preserve current fade shapes', telling the agent which attributes are left untouched. However, it says nothing about the safety/precondition machinery visible in the schema (dry_run, confirm_delete, expected_revision), which is exactly the behavioral context an agent needs before a mutation.

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?

One compact sentence with the operation front-loaded and the preservation clause second; there is no filler. The terseness is a completeness problem, not a verbosity one.

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 exists, so return values need not be described, but this is a mutation tool with a rich seven-property request object including dry-run, delete confirmation, and optimistic-concurrency fields. Omitting all of that leaves the agent unable to invoke it safely without reverse-engineering the schema.

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%, so the description carries the burden, and it only explains the sample unit for the fade values. The nested request object's dry_run, confirm_delete, and expected_revision fields — all semantically loaded — get no explanation in 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?

The description gives a specific verb+resource pair ('Set audio fade durations') plus the unit ('in samples'), which is enough to tell it apart from gain/mute/lock siblings on the same region. It stops short of explicitly naming an alternative, but the resource is unambiguous.

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?

There is no when-to-use guidance, no prerequisites, and no mention of alternatives such as trimming or other region-edit tools. An agent must infer that this is the tool for adjusting existing fade lengths, with nothing stating what to do when a region has no fades yet.

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