Skip to main content
Glama
Audionaut MCP Server

Audionaut MCP Server

Analyze audio

analyze

Runs beat, onset and segment analysis on a project or single audio file, caching results for auto_edit and assemble to use. Track progress per file and analysis type as work completes.

Instructions

Runs audio analysis (segment boundaries, beats with BPM, onsets) on the project's audio files - or one standalone audio file - and caches the results next to the project for auto_edit/assemble to use. Reports progress as each file and type finishes when the call carries a progressToken.

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": {
      "target": "<target>"
    },
    "name": "analyze"
  }
}

Input Schema

NameRequiredDescriptionDefault
typesNoComma-separated analysis types from segments, beats, onsets (default: segments,beats, what auto_edit needs)
targetYesA .audium project package or a single audio file

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.7.0
    • changedInput schema / properties / types / description
      Previous value: -"Comma-separated analysis types, e.g. \"sbic,beat_degara\" (default: the merge set)"New value: +"Comma-separated analysis types from segments, beats, onsets (default: segments,beats, what auto_edit needs)"
  2. First observedv0.2.0

TDQS

A4.1/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does disclose key behavior: it caches results next to the project and reports progress per file/type when a progressToken is present. It omits whether existing cached results are overwritten, whether analysis is idempotent, and any cost or permission implications.

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?

The description is a single, front-loaded sentence that conveys purpose, scope, caching behavior, and progress reporting without wasted words. It is dense but earns its length.

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?

For a two-parameter analysis tool with no output schema, the description gives enough context to invoke it correctly: target forms, analysis types, caching purpose, and progress behavior. It could be more complete by stating what is returned or whether re-runs overwrite prior analysis, but the core invocation path is covered.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so both parameters are already fully documented in the input schema, including the enum-like values and default for types. The description adds only the contextual note that segments,beats is what auto_edit needs, which is useful but not substantial beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

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

The description names a specific verb and resource: runs audio analysis producing segments, beats/BPM, and onsets on either project audio files or a standalone audio file. It also distinguishes its scope from unrelated siblings by stating results are cached for auto_edit/assemble. An agent can identify exactly what this tool does without opening the schema.

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

Usage Guidelines4/5

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

It makes the workflow context clear: use this to generate cached analysis that auto_edit and assemble consume. However, it does not explicitly say when not to use it or whether it is required before every auto_edit/assemble call.

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