Skip to main content
Glama
Sign In
ismail: agent DAW (MCP server)

ismail: agent DAW (MCP server)

by newsbubbles
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Analyze Melody

analyze_melody

Transcribes a monophonic stem or solo line into a note list with confidence warnings, optional cent-level pitch data, and vibrato handling.

Instructions

Monophonic pitch -> note list in notes_write format (max 16 bars). Best on a stem or a soloed line. Ends with its confidence: pYIN voicing over the notes, and a WARNING when another pitch sits within 6 dB on a quarter of the notes or more (a backing in the source: the reading can follow it, so restrict fmin/fmax). cents=True gives every note's measured pitch as numbers, for intonation and quarter tones (maqam steps): tab-separated rows start, note, dur, vel, midi (float), hz, cents from the named note. For the pitch moving inside a note (slides, vibrato, ornaments) read analyze_contour. vibrato_ms: a held note with a wide vibrato (a singer, a violin) reads as two notes a semitone apart when its centre sits near a half step; vibrato_ms=190 (one cycle, about 5 Hz) averages the pitch before rounding. It also merges trills faster than the window, so compare with analyze_roll where an ornament matters. On a full mix the loudest line wins (usually the bass): read a stem, or raise fmin over the bass.

Input Schema

NameRequiredDescriptionDefault
barsNo
fmaxNoC7
fminNoC1
centsNo
quantNo
sourceNoref:other
projectYes
min_confNo
vibrato_msNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.4.3
    • addedInput schema / properties / vibrato_ms
      Added value: +{
+  "default": null,
+  "type": "number"
+}
  2. Changed1 schema field changedv0.4.0
    • addedInput schema / properties / cents
      Added value: +{
+  "default": false,
+  "type": "boolean"
+}
  3. First observedv0.3.0

TDQS

A4.2/5.0
Behavior4/5

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

With no annotations, the description carries the behavioral burden and does well: it discloses the confidence output, warning conditions when another pitch is within 6 dB, cents output shape, vibrato averaging behavior, and full-mix behavior. It does not explicitly state that the operation is side-effect-free, but the analysis framing and output description imply a non-mutating operation.

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 dense but front-loaded with the core transformation and output format. Some sentences are long and parenthetical, but the technical detail is mostly necessary and no obvious filler is present.

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?

Given 9 parameters, no annotations, and 0% schema description coverage, the description is only partially complete. It covers the most unusual musical parameters well, but omits meaning for source, quant, min_conf, and project, which an agent may need in order to call the tool correctly.

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 0%, so the description must compensate. It explains fmin/fmax restrictions, cents output, vibrato_ms, and the 16-bar limit, but does not explain project, source, quant, or min_conf, leaving several parameters undocumented in both schema and description.

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 specific verb and resource: it converts monophonic pitch into a note list in notes_write format, with a 16-bar limit. It clearly distinguishes the tool from analyze_contour, analyze_roll, and full-mix use by explaining that contour is for pitch movement inside a note and roll is for ornaments.

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 explicitly says to use this on a stem or soloed line, and that on a full mix the loudest line wins, usually the bass. It names analyze_contour for slides/vibrato/ornaments and analyze_roll for cases where an ornament matters, giving clear alternatives and conditions.

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