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

ismail: agent DAW (MCP server)

Live Midi Clock

live_midi_clock

Send MIDI clock from the live set so Ableton, FL Studio or a drum machine locks to the set's tempo and starts on its bar line.

Instructions

Send MIDI clock from the live set to a port, so Ableton, FL Studio or a drum machine plays at the set's tempo and starts on its bar line. Reach for it when another app or a hardware box should play in time with the set. 24 pulses per quarter note at the set's tempo (one tempo per set) start at once, so the receiver can lock to it; Start goes out right before the first pulse of the next bar line, which becomes the other app's bar 1. position=True sends that bar's Song Position Pointer first and Continue instead of Start, for a DAW that follows song position (it lands on the same bar number). on=False sends Stop; the set's end sends Stop too. offset_ms: as live_midi_out (shared by the port). The other app must take clock in from that port: in Ableton, the port's Sync on (Preferences, Link/Tempo/MIDI), then EXT; in FL Studio, the port enabled as an input in MIDI settings with its sync on, then external sync. With no port: what is sending (live_status says it too).

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": "live_midi_clock"
  }
}

Input Schema

NameRequiredDescriptionDefault
onNo
portNo
projectYes
positionNo
offset_msNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.4.0

TDQS

A4.1/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 well: 24 PPQN, one tempo per set, Start emitted just before the first pulse of the next bar line, position=True sending Song Position Pointer plus Continue instead of Start, on=False and set-end both sending Stop. It also documents the downstream setup needed for the receiver to lock, which is behavior an agent cannot infer from 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.

Conciseness3/5

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

The key point is front-loaded in the first sentence, which is good. The remainder is a dense run-on paragraph mixing protocol detail, parameter semantics and receiver setup, with cryptic fragments like 'With no port: what is sending (live_status says it too)' that read as notes rather than prose.

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 five-parameter tool with no annotations, the description covers timing semantics, start/stop behavior, and receiver prerequisites, and an output schema exists so return values need not be explained. Remaining gaps are the unspecified 'project' parameter and unclear failure behavior when the port is missing or invalid.

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%, so the description must compensate, and it explains on (Stop), position (SPP + Continue), port (with the 'no port' case) and offset_ms. offset_ms is only defined by reference to live_midi_out, and the required 'project' parameter is never named, leaving small gaps.

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 opening sentence gives a concrete verb and resource: 'Send MIDI clock from the live set to a port,' plus the outcome ('plays at the set's tempo and starts on its bar line'). It does not explicitly distinguish itself from the sibling live_midi_clock_in or live_midi_out beyond referencing them for shared semantics, so sibling differentiation is only implicit.

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?

'Reach for it when another app or a hardware box should play in time with the set' gives a clear selection condition, and the receiver-configuration notes (Ableton Sync/EXT, FL Studio external sync) reinforce the scenario. There is no explicit 'do not use this when...' or a named alternative for the opposite direction, which keeps it short of a 5.

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