Ardour Ultra MCP

Overview Schema Source Related Servers Discussions Admin

convert_position

Read-onlyIdempotent

Convert a typed position between samples, seconds, musical bars/beats, or quarter ticks using Ardour's current tempo and meter map.

Instructions

Convert a typed position using Ardour's current tempo/meter map.

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

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

B3/5.0

Behavior3/5

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

The annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds useful behavioral context by saying the conversion depends on the current tempo/meter map, but it does not explain precision, error behavior, or whether changing the map changes prior conversions.

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?

The definition is a single front-loaded sentence with no filler. Every phrase, especially 'using Ardour's current tempo/meter map', contributes meaningful scope.

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?

Because an output schema exists and annotations cover the safety profile, return values and mutation risk need not be explained. However, for a tool with a nested request schema and 0% schema description coverage, the description omits the available position units, wrapper structure, and optional fields, leaving too much for the agent to infer from schema inspection alone.

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 is a nested Locate object containing a four-way discriminated position union plus optional dry_run, confirm_delete, and expected_revision fields. The description says only 'typed position', adding almost no meaning beyond the schema structure and failing to explain units or optional controls.

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 states a specific verb, 'Convert', and a clear resource, 'typed position', scoped by Ardour's current tempo/meter map. It does not enumerate the supported position units or the exact conversion result, but the purpose is still clear enough to distinguish it from track, plugin, and region tools.

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 explicit guidance on when to use this tool, when not to use it, or which alternatives apply. The conversion purpose implies its use, but the definition leaves all routing decisions to inference.

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

Deploy Server