Skip to main content
Glama
Ardour Ultra MCP
by Elias02345

list_regions

Read-onlyIdempotent

Paginate regions in an active Ardour playlist by route ID and kind, using limit and offset controls to inspect session content in manageable chunks.

Instructions

Paginate active-playlist regions by route ID and kind.

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

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

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and a closed world, so the core safety profile is supplied elsewhere. The description adds only that results are paginated; it says nothing about page-size limits, ordering, how offsets behave against a changing playlist, or why confirm_delete and dry_run appear in the payload of a read operation.

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 front-loaded sentence with no padding, which is good, but the terseness comes at the cost of precision rather than in service of it: the single clause packs in jargon and a field name that conflicts with the schema.

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?

Placeholder.

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 exposes eight nested properties, yet the description explains only 'kind' and a poorly matched 'route ID'. limit, offset, name_filter, dry_run, confirm_delete and expected_revision get no meaning from either the schema or the prose, so the description 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.

Purpose3/5

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

The verb 'paginate' plus the resource 'regions' gives a recognizable action-and-object, but 'active-playlist regions' is unexplained jargon and 'route ID' does not match the schema's 'track_id' field, leaving which identifier is required ambiguous. An agent can guess this lists regions, but cannot tell with confidence whether it differs from siblings like list_tracks or list_midi_notes beyond the object type.

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 call this versus alternatives, no prerequisite (e.g., an active playlist/route must exist), and no exclusion. The only implicit usage cue is the word 'paginate', which suggests large result sets but does not say what to do instead when the count is small.

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