Ardour Ultra MCP

Overview Schema Source Related Servers Discussions Admin

create_midi_region

Create a blank internal MIDI region on a specified track with a name and precise start/end positions. Use it to add editable MIDI clips to an Ardour Editor session.

Instructions

Create a blank internal MIDI region in Editor context.

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

Input Schema

Name	Required	Description	Default
`request`	Yes

Output Schema

Name	Required	Description	Default
`data`	No
`error`	No
`success`	No
`warnings`	No
`revision_after`	No
`changed_objects`	No
`revision_before`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Nov 9, 2026

TDQS

C2.7/5.0

Behavior2/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, idempotentHint=false and openWorldHint=false, so the safety profile is partly covered. However, the schema exposes dry_run, expected_revision and confirm_delete fields whose behavior (optimistic concurrency checks, preview mode, delete confirmation) is never explained, which is a real gap for a mutation tool. 'Blank' is the only behavioral fact added, namely that the region contains no notes.

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?

A single front-loaded sentence with no filler or redundancy. It is efficient, though the brevity borders on under-specification rather than tightness.

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 the description leaves a mutation tool with a seven-field request, an unusual confirm_delete parameter on a create operation, and a revision-concurrency control entirely undocumented. Relative to that complexity, one sentence is not enough for an agent to call it safely.

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 top-level parameter is a nested request object with seven fields (track_id, name, start, end, dry_run, expected_revision, confirm_delete) and four position encodings. The description supplies no meaning for any of them, so an agent must read the JSON schema to learn even that positions can be expressed in ticks, samples, seconds or bars/beats.

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 ('Create a blank internal MIDI region') plus a scoping qualifier ('in Editor context'), so an agent knows this produces a new empty region rather than copying or importing one. It does not name any sibling (copy_region, insert_midi_notes, etc.) to sharpen the boundary, and 'internal'/'Editor context' is left unexplained.

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 when-to-use or when-not-to-use guidance is given. Nothing tells the agent how this differs from copy_region or from inserting notes into an existing region, and no prerequisites (track must exist, editor must be open) are stated.

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

Deploy Server