Skip to main content
Glama
Ardour Ultra MCP
by Elias02345

doctor

Read-onlyIdempotent

Inspects runtime, bridge, paths, and optional analysis dependencies to verify the Ardour Ultra MCP environment before editing or analyzing a session.

Instructions

Inspect runtime, bridge, paths and optional analysis dependencies.

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

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=true, idempotentHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds that the inspection spans runtime, bridge, paths, and optional analysis dependencies, which is useful scoping context. It does not say whether missing dependencies cause an error or are simply reported, and the awkward 'Empty' request object is never explained.

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?

A single short, front-loaded sentence with no filler. It is efficient, though the compressed noun list ('runtime, bridge, paths') is slightly cryptic for an agent unfamiliar with the domain.

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

Completeness5/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 in the description, and annotations fully cover the read-only, idempotent, closed-world behavior. For a one-parameter diagnostic tool, what remains is adequately covered, with only the odd request fields left unaddressed.

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 parameter is a nested 'Empty' object exposing dry_run, confirm_delete, and expected_revision — generic-looking fields that are counterintuitive for a read-only diagnostic. The description adds no meaning about this 'request' object or which of its fields matter, so it fails to compensate for the zero coverage.

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?

"Inspect runtime, bridge, paths and optional analysis dependencies" gives a verb and a list of inspected subjects, so the general purpose (a diagnostic/health check) is inferable. However, it never states that this is a diagnostics tool or distinguishes it from siblings such as get_server_info, get_capabilities, or get_session_info, which an agent could easily confuse with it.

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 at all: nothing says whether this should be called before other operations, when troubleshooting, or instead of get_server_info/get_session_info. The phrase "optional analysis dependencies" hints at a precondition check but never tells the agent under what circumstances to invoke it.

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