Ardour Ultra MCP

Overview Schema Source Related Servers Discussions Admin

analyze_audio_file

Read-onlyIdempotent

Analyze audio files offline to measure peak, RMS, LUFS, spectrum, stereo, silence, and estimated true peak, limited to allowed roots for audio quality checks.

Instructions

Offline peak/RMS/LUFS/spectrum/stereo/silence and estimated true peak; allowed roots only.

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

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

B3.1/5.0

Behavior4/5

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

Annotations already cover readOnly, idempotent, closed-world and non-destructive, so the bar is lower, and the description still adds real value: 'offline' signals non-realtime file-based measurement, 'estimated true peak' warns the true-peak figure is an approximation, and 'allowed roots only' discloses a path sandbox constraint the agent must respect. It omits what happens when a path falls outside the allowed roots and that max_seconds truncates the analysis.

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 dense line with no filler, and the measured quantities are front-loaded before the constraint clause. The telegraphic fragment style (no verb, semicolon-joined clauses) costs a little readability but wastes nothing.

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, and annotations carry the safety profile. However, for a tool whose parameters include a duration cap and a delete-confirmation flag, the description never addresses parameter behavior or the truncation/approximation caveats an agent needs to interpret results correctly.

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 description says nothing about the request fields. It does not explain path, max_seconds (a 600s default truncation that materially changes results), expected_revision, or the surprising confirm_delete flag on a read-only tool. With one required nested object and five fields, the description leaves all semantic burden on bare titles.

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?

The description names the specific measurements produced (peak, RMS, LUFS, spectrum, stereo, silence, estimated true peak) and marks the operation as offline, which distinguishes it from realtime siblings like get_meter_state. It never states an explicit verb such as 'analyze a file at the given path', but the resource and output set are unambiguous.

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 or when-not-to-use guidance and no mention of the obvious alternative, compare_audio_files, or of render_and_analyze. The only routing signal is the word 'offline', which an agent must infer means 'analyzing an existing file rather than a live session'.

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

Deploy Server