@audiolabtools/mcp-server

Loudness over time (for graphing / visualization)

analyze_timeseries

Extract short-term LUFS loudness samples and downsampled waveform peaks from public audio URLs or local files for charts, meters, and waveform UIs.

Instructions

Short-term LUFS samples over time (EBU R128, ~3s window) with their time-base, plus downsampled waveform peaks. Arrays suitable for loudness-over-time charts, level meters, and waveform UIs. Audio source: a public https URL, or a local file path (path).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "analyze_timeseries"
  }
}

Input Schema

Name	Required	Description
`url`	No	Public https URL to the audio file. Provide exactly one of url or path.
`path`	No	Path to a LOCAL audio file on this machine, analysed without hosting it publicly (files up to 4 MB are sent inline; larger ones up to 150 MB upload over a signed URL). Provide exactly one of url or path.
`waveformPoints`	No	Waveform peak count (default 200).

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 6, 2026

TDQS

B3.4/5.0

Behavior3/5

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

With no annotations, the description carries the full burden. It usefully discloses the ~3s analysis window, the EBU R128 standard, and that the waveform is downsampled, but says nothing about response size limits, error behavior, or processing cost. Partial disclosure for a read-only analysis tool.

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?

Three tight sentences that front-load what is returned, then the applicability, then the input sources. No filler, though the last sentence partially duplicates what the schema already documents.

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

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

There is no output schema and no annotations, so the description should fully explain the return shape. It names the arrays and time-base but omits units, ordering, or pairing format between samples and timestamps, leaving moderate gaps for an agent consuming the result.

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 description coverage is 100%, so the baseline is 3. The description restates the two audio-source options (public https URL or local path) but adds no syntax or format detail beyond the schema, and the `waveformPoints` parameter is only hinted at via 'downsampled waveform peaks' without naming the default or unit.

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 a specific resource (short-term LUFS samples with time-base, plus downsampled waveform peaks) and specifies the measurement standard and window (EBU R128, ~3s). It implicitly distinguishes itself from analyze_loudness by framing output as arrays for charts/meters rather than summary metrics, but never names the sibling explicitly.

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?

It gives use-case context (loudness-over-time charts, level meters, waveform UIs) and lists both audio sources, but there is no explicit 'use this instead of analyze_loudness when...' routing and no when-not guidance. The consumer must infer that this tool is for time-series data versus summary statistics.

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

This server cannot be deployed