Skip to main content
Glama
Ardour Ultra MCP
by Elias02345

get_region

Read-onlyIdempotent

Retrieves a region's ID, playlist, source offset, timeline position, and length from an Ardour session for inspection and precise editing.

Instructions

Read region ID, playlist, source offset, timeline position and length.

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

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.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds only the notion that this is a pure read of specific fields. Notably it does not explain why a read tool's schema carries dry_run, confirm_delete and expected_revision fields, which could confuse an agent about side effects.

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?

One tight sentence with no filler, which is good. But it is a bare field list with no framing sentence, so it is under-specified rather than genuinely concise.

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

Completeness3/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 explanation, and a read-only single-region getter is inherently simple. Still, the undocumented nested request parameters and the unaddressed mutation-flavored fields leave real gaps for an agent constructing the call.

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 object nests five properties. The description only vaguely gestures at region ID and playlist, leaving track_id, expected_revision, dry_run and confirm_delete entirely unexplained. With low coverage the description should compensate, and it 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?

Uses a specific verb ("Read") with a named resource (region) and enumerates the fields returned — region ID, playlist, source offset, timeline position, length. That distinguishes it from mutating siblings such as move_region or trim_region, though it never states outright that it retrieves a single region's details.

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: nothing says it requires a track_id plus region_id, nor how it differs from get_track or get_session_info when an agent just needs context. The agent must infer selection from the name alone.

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