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

ismail: agent DAW (MCP server)

Midi Write

midi_write

Exports a song or selected bars to a Standard MIDI File, with tracks, tempo, meter, markers, lanes, and program changes for DAWs, hardware sequencers, or MPE synths.

Instructions

Write the song's notes to a Standard MIDI File (type 1) that Ableton, FL Studio, Logic, Reaper, MuseScore and any hardware sequencer open: one MIDI track per ismail track that has notes (named after it), the tempo, the meter, and markers. tracks: names to include (default every track with notes, muted ones too). bars: [a, b] writes only notes that start in those bars, moved so bar a is the file's bar 1 (default the whole song, bar 1 at the start). markers: {name: bar}, e.g. {'drop': 17}, shown as locators in the DAW. Nudged notes (@offset, a track's offset_ms) land where they sound, to the nearest tick (about 0.5 ms at 120 BPM). Kits go on channel 10 with ismail's own pad pitches (the reply lists which pitch is which pad); other tracks get channels 1 to 16 in order. The file carries notes, not sounds: in the DAW, put an instrument on each track. out: the file (default /exports/.mid). A track's expression lanes (automation inst.lane.) go out as MIDI on its channel: bend as pitch bend (+-2 semitones, said in the file with RPN 0), vib as cc:1 (mod wheel, 0..50 cents), level as cc:11 (expression, -40..0 dB, 127 the fader), breath as cc:2 (0..1). lanes: overrides as data, {lane: {'midi': 'bend' | 'pressure' | 'cc:', 'range': [lo, hi]}} (the lane's values at the message's ends; a bend range is [-r, r] or r), or {lane: None} to leave one out; e.g. {'bend': {'range': 12}, 'mute': {'midi': 'cc:20', 'range': [0, 1]}}. The reply names lanes with no message and values clamped to a range. mpe: the tracks written as MPE, for an MPE synth: each note on its own member channel with the track's lanes over its own span (bend +-48, level as per-note channel pressure), after the MPE configuration (RPN 6). True or 'lower' (every melodic track in the lower zone: channel 1 the master, members 2 to 16), 'upper' (the upper zone: channel 16 the master, members 15 down to 1), a list of track names (the lower zone), or {track: 'lower' | 'upper'} (a split synth: with both zones in the file each has 7 members, 2-8 and 9-15). The other tracks get channels outside the zones: a kit keeps channel 10, and a zone shrinks (to 4 members at least) to leave each plain track a channel; the reply says how far. No poly pressure goes out: a song's lanes are per track, with no per-note pressure to carry (mpe= gives each note its own channel pressure instead). programs: a GM program change per track, 1 to 128 as a GM list numbers them (1 piano, 33 acoustic bass, 81 square lead), so a GM synth or a DAW's GM player picks the sound: {'bass': 33}, or a program per bar where the sound changes, {'lead': {1: 81, 17: 82}}. With bars=, the program in force at the first bar goes at the file's start. A track has no program of its own in ismail (its sound is its instrument), so a track left out has none. Reach for it when the person wants to export or write the song or a part as MIDI for their DAW, a hardware sequencer or an MPE synth, its lanes as pitch bend and controllers, its program changes.

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": {
      "project": "<project>"
    },
    "name": "midi_write"
  }
}

Input Schema

NameRequiredDescriptionDefault
mpeNo
outNo
barsNo
lanesNo
tracksNo
markersNo
projectYes
programsNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv0.4.5
    • addedInput schema / properties / lanes
      Added value: +{
      +  "additionalProperties": true,
      +  "default": null,
      +  "type": "object"
      +}
    • addedInput schema / properties / mpe
      Added value: +{
      +  "default": null,
      +  "title": "Mpe"
      +}
    • addedInput schema / properties / programs
      Added value: +{
      +  "additionalProperties": true,
      +  "default": null,
      +  "type": "object"
      +}
  2. Addedv0.4.0

TDQS

A4.3/5.0
Behavior4/5

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

With no annotations, the description bears the full burden and delivers substantial behavioral detail: track/channel allocation (kits on channel 10, others 1-16), the caveat that the file carries notes not sounds, MPE zone shrinking to free channels, and that reply data names unmapped lanes and clamped values. It omits failure modes (invalid project, write permission on the export path) and doesn't explain the required 'project' scoping, leaving some gaps.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The content is dense and nearly every sentence carries real information, but it is delivered as one massive unbroken paragraph with no headings or line breaks, hurting scanability. The critical usage trigger is buried at the very end rather than front-loaded, so the structure undersells otherwise valuable content.

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 an 8-parameter tool with nested objects and 0% schema coverage, the description is remarkably complete on channels, lanes, MPE, programs and output defaults. Since an output schema exists, return values need not be described. The main hole is the sole required parameter 'project', which is never explained, leaving the agent to infer its meaning.

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

Parameters5/5

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

Schema coverage is 0%, and the description compensates comprehensively for every optional parameter: bars as [a, b] with bar-remapping semantics, markers as {name: bar} with a 'drop': 17 example, tracks inclusion and muted handling, out default path, lanes override grammar with a concrete example, mpe accepting True/'lower'/'upper'/list/dict plus zone-mate math, and programs with GM numbering examples. This is far beyond what the bare schema provides.

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?

States a specific verb and resource up front: writes the song's notes to a Standard MIDI File (type 1), naming the DAWs and hardware that open it. This clearly distinguishes it from siblings like midi_play, render or live_midi_out, which do not produce a portable .mid export. An agent can identify the operation without inspecting 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?

The closing sentence supplies an explicit trigger: 'Reach for it when the person wants to export or write the song or a part as MIDI for their DAW, a hardware sequencer or an MPE synth.' It gives clear context but does not name an alternative (e.g. render, midi_play) or state when not to use it, so the guidance is strong but not a full when/when-not matrix.

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