Skip to main content
Glama
Ardour Ultra MCP
by Elias02345

locate

Move the Ardour playhead to an exact position using samples, seconds, quarter ticks, or bar-beat-tick coordinates, with optional dry-run validation.

Instructions

Locate using typed samples, seconds, quarter ticks or BBT.

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

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.1/5.0
Behavior2/5

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

Annotations declare readOnlyHint=false and idempotentHint=false, implying a state-mutating operation, yet the description says nothing about what state changes or whether it is reversible. The presence of dry_run, confirm_delete and expected_revision arguments signals meaningful safety behavior (a confirmation gate and optimistic concurrency) that the description completely ignores.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is a single front-loaded sentence fragment with no filler, so it is certainly concise. However, the brevity comes from omission rather than economy: the fragment lacks an object for its verb and omits the flags that determine safe invocation.

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 for a non-read-only tool with dry-run/confirm-delete/revision arguments the definition leaves the agent without enough to call it safely or confidently. Nothing explains position validity, ordering, or what happens when expected_revision mismatches.

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, but it only echoes the four position unit names already encoded in the discriminator mapping. The dry_run, confirm_delete and expected_revision flags — the ones an agent most needs explained before calling — get no mention at all.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

"Locate" names a verb but never states the object: it does not say what is being located (transport/playhead, cursor, region?) or what the operation does to session state. The only added content is the list of position units, which merely restates the schema's unit variants rather than clarifying the action.

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 reference to any alternative such as the sibling convert_position, which plausibly handles unit conversion without moving anything. The agent must infer from the name alone whether this moves the playhead or just resolves a position.

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