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

ismail: agent DAW (MCP server)

Live Map

live_map

Maps a knob, fader, pad, footswitch, or MPE/aftertouch control to a live DAW parameter or trigger action, so moves apply directly in the engine without an agent.

Instructions

Map a named control (a knob, slider or switch on the VR stage, any client, or a MIDI controller's knob, fader, pad or bend wheel) to a live parameter, so its moves apply in the engine at once with no agent in the loop. target: a track, 'bus:' or 'deck:'. param: 'volume_db', 'pan' (tracks), a deck's 'low_db'/'mid_db'/'high_db'/'filter'/'volume_db', or an effect param 'fx:.' ('fx:filter.cutoff', 'fx:delay.mix'). The control sends 0..1; range=[value at 0, value at 1]; curve 'linear', 'log' (Hz, ratios), 'switch' (below 0.5 = the first value), or 'raw' (the value passes in the param's own units; not for MIDI). at: when a move lands for effect and deck params ('now', 'next_bar'). Every move is logged by bar: live_controls reads them back as automation. remove=True unmaps. MIDI as the source: midi='cc:<0-127>' (a knob or fader, 0..127 as 0..1), 'cc14:<0-31>' (a 14-bit pair, MSB n and LSB n+32), 'bend' (the wheel; centre = 0.5), 'pressure' (channel aftertouch), 'note:<36 or C2>' (a pad: held = 1, released = 0), 'program:<1-128>' (a program change, numbered from 1 as a GM list or the controller's screen shows it: a footswitch or a preset button; it fires an action, or with mode='toggle' flips a param), 'poly' (polyphonic aftertouch: the hardest-pressed key held) or 'poly:<60 or C4>' (that key's), or 'mpe:pressure', 'mpe:bend', 'mpe:timbre' (an MPE note's own pressure, bend or cc:74, the newest note held winning, on the member channels of the zone the input plays in: live_midi(mpe=...) or the controller's own MPE configuration, else the lower zone; no channel=). A poly or mpe map takes that expression only: the keys still play. source: the MIDI input (midi_sources; optional when there is one), opened by the map even when no keys are patched; channel: 1 to 16 (default every channel). mode: 'absolute' (the param jumps to the knob), 'pickup' (it moves only once the knob reaches the param's value, so nothing jumps after the agent or the stage moved it), 'relative' (an endless encoder sending two's complement steps, 1..63 up, 127..65 down) or 'relative64' (64 = still, 65 up, 63 down), each step 1/128 of the range (step= sets it per map: 1/32 for a coarse encoder, 1/512 for a fine one), from the param's value now (fast steps add up). accel: a fast turn moves further, as on a hardware synth's encoder: a tick 0.1 s or more after the last moves one step, a faster one more (twice as fast, twice as far), up to accel steps (above 1, at most 16; True = 4). Off by default; live_status shows it. Use it when one encoder must both sweep the range quickly and set it finely. 'toggle' (a pad or a button flips between the range's ends on each press: 64 or more after a release, or a repeat 0.1 s or more after the last with no release). Several maps may share one MIDI control (one knob, several params; reverse a range to move one the other way). A bound message is a control, not a key: it is not played or logged by live_midi. Not sure what a knob sends? live_controls(source=) listens. A pad or a button as a trigger: action= instead of target and param fires a command on each press (a note-on, a 'cc:' button reaching 64, or that program change; the release does nothing), with no agent in the loop. The actions, as data with the arguments of the op they mirror: {'op': 'live_queue', 'clips': [...], 'section': ..., 'cancel_section': ...} (a scene or a part: the clips, stops and section cut-over queue on each press, each clip at its own 'at', default the next bar), {'op': 'live_tempo', 'bpm': 128, 'at': 'next_bar'}, {'op': 'live_transition', 'to': 'B', 'bars': 16, 'style': 'blend'}. The tracks and decks it names are checked when it is mapped; the reply of each press comes in the engine's news, and live_controls lists the presses by bar. Mute a track from a pad with a param map: target=, param='volume_db', range=[0, -120], curve='switch', mode='toggle'. live_control (value=1) fires an action map too. Reach for it when the person wants a knob, fader, pad, footswitch, the pressure on a key (aftertouch) or an MPE note's own slide or pressure on their controller to move something in the set.

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>",
      "control": "<control>"
    },
    "name": "live_map"
  }
}

Input Schema

NameRequiredDescriptionDefault
atNonow
midiNo
modeNoabsolute
stepNo
accelNo
curveNolinear
paramNovolume_db
rangeNo
actionNo
removeNo
sourceNo
targetNo
channelNo
controlYes
projectYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed7 schema fields changedv0.4.5
    • addedInput schema / properties / accel
      Added value: +{
      +  "default": null,
      +  "title": "Accel"
      +}
    • addedInput schema / properties / action
      Added value: +{
      +  "additionalProperties": true,
      +  "default": null,
      +  "type": "object"
      +}
    • addedInput schema / properties / channel
      Added value: +{
      +  "default": null,
      +  "type": "integer"
      +}
    • addedInput schema / properties / midi
      Added value: +{
      +  "default": null,
      +  "type": "string"
      +}
    • addedInput schema / properties / mode
      Added value: +{
      +  "default": "absolute",
      +  "type": "string"
      +}
    • addedInput schema / properties / source
      Added value: +{
      +  "default": null,
      +  "type": "string"
      +}
    • addedInput schema / properties / step
      Added value: +{
      +  "default": null,
      +  "type": "number"
      +}
  2. Addedv0.4.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 full burden and discloses many operational traits: immediate engine application, bar-based logging, live_controls reading moves back as automation, remove=True unmapping, MIDI input being opened even without patched keys, and bound messages not being played or logged by live_midi. It does not fully cover prerequisites, failure behavior for invalid mappings, or persistence.

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 purpose is front-loaded and most content is relevant given 15 undocumented parameters. However, the definition is a very dense wall of text with long parenthetical enumerations, making it hard to scan despite little obvious repetition.

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 complex tool with no annotations, 15 parameters, 0% schema coverage, and an output schema, the description is remarkably complete about mapping behavior, MIDI modes, and action maps. It is still missing project semantics and exact control naming, and it does not state engine prerequisites or error conditions.

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 description coverage is 0% across 15 parameters, so the description must compensate, and it explains target grammar, param grammar, range, curve, at, remove, MIDI message forms, source, channel, mode, step, accel, and action objects in detail. The notable gaps are the required project parameter, which is never described, and the exact string form expected for the required control parameter.

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 opening states a specific verb and resource: map a named control to a live parameter so moves apply immediately. It also distinguishes the tool from live_controls (readback of logged moves), live_control (fires an action map), and live_midi (keys are not bound or logged).

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 gives clear usage contexts, including 'Use it when one encoder must both sweep the range quickly and set it finely' and 'Reach for it when the person wants a knob, fader, pad, footswitch...' It also points to live_controls when the incoming MIDI message is unknown, but it does not provide explicit when-not-to-use 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