Skip to main content
Glama
Ardour Ultra MCP
by Elias02345

list_ports

Read-onlyIdempotent

Retrieve paginated engine port names and connections with backend-qualified IDs for inspecting Ardour routing.

Instructions

Paginate engine port names and connections; port IDs are backend-qualified names.

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

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.7/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 a closed-world scope, so the safety profile is fully covered. The description contributes one genuinely useful behavioral fact, that port IDs are backend-qualified names, which matters downstream when calling connect_ports, but it says nothing about ordering, page size defaults, or what happens at the end of the collection.

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

Conciseness4/5

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

One compact sentence with the resource stated first and the ID-format caveat second; nothing is padded or redundant. It is short to the point of under-specification, but not wordy.

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 the input side is entirely undocumented despite six nested fields with zero schema coverage. For a paginated listing tool that feeds connect_ports, the description should at minimum explain filtering and paging; as written an agent must guess.

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 expands into limit, offset, dry_run, name_filter, confirm_delete and expected_revision with no documentation anywhere. The description adds no meaning to any of these, and it does not clarify that name_filter is the way to narrow results or that confirm_delete is presumably inert for a read-only listing.

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 description names the resource (engine ports) and adds what is returned (names and connections), so the agent knows it is a listing tool. However, 'Paginate' as the leading verb frames a mechanism rather than an action, and there is no explicit differentiation from siblings such as connect_ports or disconnect_ports beyond the obvious verb mismatch.

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?

No when-to-use or when-not-to-use guidance is given, and no prerequisite context is stated. The description does not mention that this is the discovery step that precedes connect_ports/disconnect_ports, which would be the natural routing hint.

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