Skip to main content
Glama
Ardour Ultra MCP
by Elias02345

get_transport

Read-onlyIdempotent

Reads the current playhead position in samples along with transport speed, loop status, and recording state so agents can inspect an Ardour session before editing.

Instructions

Read playhead in samples, speed, loop and recording state.

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

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

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered. The description adds which transport values are returned, which is genuine extra context, but says nothing about snapshot timing, whether values update during playback, or how the oddly mutation-flavored request envelope behaves on a read.

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?

A single front-loaded sentence listing the returned values with no filler. Nothing could be removed without losing information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/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 no elaboration, and this is a simple read tool with one wrapped parameter. The description covers the read surface adequately. The remaining gap is the unexplained request envelope, which matters little for calling but is a mild inconsistency.

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% for the single 'request' parameter, and the description says nothing about it. The schema exposes dry_run, confirm_delete and expected_revision fields that are counterintuitive on a read-only getter, and the description does not explain why they exist or whether they are ignored. With zero coverage the description is expected to compensate and does not.

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 gives a specific verb ('Read') plus the resource's field surface: playhead position in samples, speed, loop and recording state. An agent immediately knows this is a transport-status snapshot. It stops short of naming or differentiating itself from sibling getters such as get_session_info or get_meter_state, so it does not reach 5.

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 statement of prerequisites, and no pointer to an alternative for related queries like tempo or session metadata. The read-only framing implies a status check, but the agent must infer that entirely.

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