Ardour Ultra MCP

Overview Schema Source Related Servers Discussions Admin

set_monitoring

Idempotent

Set a track's monitoring mode to auto, input, or disk in an Ardour session so you can control what audio is heard during recording and playback.

Instructions

Set track monitoring: auto/input/disk.

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

Input Schema

Name	Required	Description	Default
`request`	Yes

Output Schema

Name	Required	Description	Default
`data`	No
`error`	No
`success`	No
`warnings`	No
`revision_after`	No
`changed_objects`	No
`revision_before`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Nov 9, 2026

TDQS

C2.6/5.0

Behavior2/5

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

Annotations already declare non-read-only, idempotent, non-open-world and non-destructive, so the safety profile is covered structurally. The description adds nothing beyond that, and it is notably silent on the schema's dry_run, confirm_delete and expected_revision fields, which imply a previewable and possibly consequential change that the agent needs warning about.

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 short, front-loaded sentence with no filler, which is good structurally. The problem is under-specification rather than wordiness, so it is efficient but not adequately sized for a mutation tool with a five-field request.

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. Still, for a mutating tool exposing dry_run, confirm_delete and expected_revision, the description leaves the agent with no model of the operation's behavior or side effects, which is a real completeness gap.

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 fields. The description only restates the mode enum values; it explains nothing about track_id format, what dry_run previews, and especially what confirm_delete would delete in a tool annotated destructiveHint=false.

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?

Names a verb ("Set") and a resource ("track monitoring") plus the three available modes, which is more than a tautology. However, it never explains what track monitoring actually governs (input vs. disk vs. auto monitoring of recorded audio), so the agent knows the object but not the effect.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The implied usage is to change a track's monitoring mode, and no sibling tool overlaps that capability, so an agent can route here without an explicit alternative. There is no statement of prerequisites, when-not-to-use, or how it relates to arming or recording tracks.

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

Deploy Server