Ardour Ultra MCP

Overview Schema Source Related Servers Discussions Admin

set_tempo

Idempotent

Insert a constant quarter-note BPM tempo point at an exact position, specified in bars/beats, seconds, samples, or ticks, to control playback timing in an Ardour session.

Instructions

Insert constant quarter-note BPM point at a typed position.

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

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 this as a non-read-only, idempotent, non-destructive write. The description adds only that the tempo is constant (no ramp), but says nothing about the dry_run flag, confirm_delete, or the expected_revision optimistic-concurrency check, all of which materially change how the tool behaves when called.

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 wasted words. It is efficient, though its terseness is part of why important behavioral details are absent.

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 are present, so return values and safety profile are partly covered. However, for a mutation tool with a nested request containing dry-run, delete confirmation, and revision checks, the description leaves too much unexplained for an agent to call it safely and correctly.

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?

The single request object carries nested fields (bpm, position with four unit variants, dry_run, confirm_delete, expected_revision) at 0% description coverage in the schema. The description only hints at "BPM" and "typed position" and explains none of these controls, so it fails to 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?

"Insert constant quarter-note BPM point" names a specific verb and resource, and the qualifiers "constant" and "quarter-note" narrow it to a particular kind of tempo marker. It does not explicitly contrast with nearby siblings like set_time_signature or create_automation_points, but the intent 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 statement of when to use this tool versus alternatives, no prerequisites (e.g., confirmation or dry-run conventions), and no note about overwriting an existing tempo at the same position. An agent must infer everything from the one sentence.

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

Deploy Server