Skip to main content
Glama
newsbubbles

ismail: agent DAW (MCP server)

Sound Zoom Diff

sound_zoom_diff

Pinpoints where a test audio render differs from reference takes beyond their natural spread, listing hot-spot text and outlining spots in a PNG. Use it to locate wrong word parts or verify fixes.

Instructions

Where a sound differs from what it should match, beyond the reference's own take-to-take spread: hot-spot text first (scale, band, quarter of the word, brighter or darker, z, the control rate in the same cell), then a PNG (at most 1600 px) of the test above the anchor take with the spots outlined. Reach for it when you need to find where my render, synth or copy differs from the real takes, which part of a word is wrong, or whether a fix closed a spot. test: the source under test; refs: >= 3 sources, takes of the same words (3 give the spread; a 4th makes the own-source control: each take in the test's place, judged by the takes that are neither). With 3 the spots are listed uncontrolled and none is counted; with fewer it refuses, as there is no absolute threshold to fall back on. seconds: [t0, t1] of the word in test (s in the file; None = the whole file); ref_seconds: one [t0, t1] per ref (default: test's, for a clip timed from a take). anchor: the ref the test is compared with. f_lo/f_hi: list spots only in this band (Hz). level_lufs: every clip is set to this loudness first, then kept under a 0.89 peak (whole file, vox's loud at -25 LUFS); None when you level-matched them yourself. Cut long files to the line first: the level match and the spread assume one line of words. Measured on power (blur and band means of power, then dB), never on mean of dB. z is in units of the reference's own spread per time-frequency cell, at three scales: grain (cells), strokes, plumes. A spot counts only where the control lights its cell less often than the test does; every spot shows its control rate and whether it is beyond every control spot in that cell. debias=True removes a smooth per-band offset, so a deficit across a whole band is absorbed and does not show as a spot: for a band-wide level run debias=False or read region_measure on the band. params: zoom.DEFAULTS overrides (z_thr, min_cells, top_spots, ...); the defaults are the tested method.

Input Schema

NameRequiredDescriptionDefault
outNo
topNo
f_hiNo
f_loNo
refsYes
testYes
wordNo
anchorNo
debiasNo
paramsNo
projectYes
secondsNo
level_lufsNo
ref_secondsNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.4.0

TDQS

A4.7/5.0
Behavior5/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 so thoroughly: it discloses output order and format, PNG size cap, the >=3 refs refusal behavior, level matching and peak limiting, measurement on power/dB, z units, control-rate logic, and the effect of debias. These are meaningful behavioral traits beyond the schema.

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 front-loaded with the core purpose, output format, and when to use it, and most sentences add relevant technical or behavioral detail for a complex analysis. It is dense with parentheticals and long clauses, but given the algorithm and 14 parameters, little appears to be pure filler.

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?

The tool is complex and has no annotations, but the description covers the essential computation, constraints, outputs, and caveats, and an output schema exists for return structure. It is still missing explicit meaning for several parameters, especially the required project and the word/top/out controls, which keeps it from being fully self-contained.

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

Parameters4/5

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

Schema coverage is 0%, so the description must compensate, and it explains many non-obvious parameters in depth: test, refs, seconds, ref_seconds, anchor, f_lo/f_hi, level_lufs, debias, and params overrides. However, it leaves project, out, top, and word unspecified, which is a notable gap for a 14-parameter tool with no schema descriptions.

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 states a precise analysis: finding where a test sound differs from reference takes beyond the reference's own take-to-take spread. It names concrete outputs (hot-spot text and a PNG with spots outlined) and clearly distinguishes this from a general zoom or band-level measurement by mentioning region_measure as the alternative for band-wide level runs.

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

Usage Guidelines5/5

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

It gives explicit triggers: use when needing to find where a render, synth, or copy differs, which part of a word is wrong, or whether a fix closed a spot. It also states constraints and alternatives, including the >=3 refs requirement, the refusal below that, the benefit of a 4th reference for controls, and using debias=False or region_measure for band-wide level issues.

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

Deploy Server

Other Tools