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

ismail: agent DAW (MCP server)

Midi Ports

midi_ports

Lists the MIDI input and output ports on this computer by name so you can route keyboards, synths, virtual ports, and DAW connections to live playback, clock, timecode, or note output.

Instructions

The MIDI ports this computer has now, by name: inputs (keyboards, pads, virtual ports that send to ismail) and outputs (synths, sound modules, loopMIDI or IAC ports into a DAW, that ismail sends to). Inputs play through a live set with live_midi, or lead its tempo with their clock (live_midi_clock_in) or its place with their timecode (live_midi_timecode_in); outputs take a live track's notes (live_midi_out), the set's clock (live_midi_clock) or its timecode (live_midi_timecode), or a song's notes from here (midi_play). On Windows, loopMIDI makes a virtual port that is both: ismail sends to it, and the DAW takes it as an input.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "midi_ports"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.4.0

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations at all, the description carries the full load. It does signal snapshot semantics via 'has now', which hints the result reflects current device state and may change, and it adds platform-specific detail about Windows loopMIDI being both an input and an output. It does not say whether the call triggers a device rescan, whether results are cached, or what happens if no devices are present.

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 core purpose is front-loaded in the first clause, which is good. But the single paragraph then chains seven sibling tool names and a parenthetical aside about loopMIDI, making it dense and hard to scan; the consumer list could be compressed or bulleted.

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?

An output schema exists, so return values need no explanation, and the description compensates by explaining the input/output categories and what each is used for. What remains thin is the relationship to midi_sources and any statement about refreshing device state, but for a zero-parameter listing tool this is close to complete.

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?

The tool takes zero parameters, so there is nothing for the description to disambiguate and the baseline of 4 applies. The phrase 'by name' usefully implies the returned names are the identifiers other tools expect.

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 specific verb and resource: the MIDI ports the computer has now, split into inputs and outputs with examples of each. The verb+resource pairing plus the input/output taxonomy makes the purpose unmistakable, though it never addresses how it differs from the sibling midi_sources, which an agent may see as an overlapping lookup.

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

Usage Guidelines3/5

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

Usage is conveyed indirectly by mapping each port category to the tools that consume it (live_midi, live_midi_clock_in, live_midi_timecode_in, live_midi_out, live_midi_clock, live_midi_timecode, midi_play). That tells an agent what the port names are good for, but there is no explicit instruction like 'call this first to discover port names before configuring live_midi', nor any exclusion against midi_sources.

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