Skip to main content
Glama
Ardour Ultra MCP
by Elias02345

trim_region

Trims an Ardour region to exact absolute timeline start and end bounds, enabling precise shortening or extension while keeping native undo available.

Instructions

Trim to absolute timeline bounds within original region; native undo.

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": "trim_region"
  }
}

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 state the operation is non-read-only, non-destructive, non-idempotent, and closed-world; the description adds the useful fact that changes support native undo and are bounded by the original region. It does not explain dry_run, confirm_delete, expected_revision, or what happens to region contents beyond the bounds.

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?

The description is a single front-loaded sentence with no wasted words, and 'native undo' adds useful context. Its terseness becomes cryptic in places, especially 'absolute timeline bounds within original region'.

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 mutation tool with a nested request object, several optional safety parameters, and no schema descriptions, the definition is too thin to guide correct invocation. Output schema and annotations cover return format and safety profile, but key parameter and usage details are missing.

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 must carry parameter meaning. It only implies start/end bounds and region identity; it leaves track_id, start/end unit discriminators, dry_run, confirm_delete, and expected_revision completely unexplained.

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?

Names a specific verb ('Trim') and resource ('region'), and describes the bound target ('absolute timeline bounds within original region'). It does not distinguish from siblings such as split_region or delete_region, so it is clear but not sibling-differentiating.

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?

Gives no when-to-use guidance, prerequisites, or alternatives; 'native undo' describes behavior rather than selection criteria. An agent must infer when trimming is appropriate versus splitting or editing region bounds another way.

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