ismail: agent DAW (MCP server)

Overview Schema Source Related Servers Discussions Admin

Live Device

live_device

Move a running audio set to another output device without stopping playback, keeping the timeline, queue and mixed audio intact. Set follow mode or switch output off mid-set with no restart.

Instructions

Move a running set to another audio output without stopping it: the timeline, the queue and the audio mixed ahead carry on, with a gap of about a second. device: 'default' (the system's default output now: use it after connecting a Bluetooth speaker), a name or part of one ('JBL'), an index, or 'none'. With device 'default' the engine also follows the system default by itself (checked every few seconds; follow=False stops that), and a device that stops taking audio (a speaker switched off) falls back to the default. reopen=False only sets follow and stays on the output it has (no gap); the phone page's Output switch does the same. device='none' turns the room speaker off mid-set (listening on the phone instead): the clock, the queue, streams, recording and live_listen carry on, and device='default' (or a name) turns it back on, no restart.

Input Schema

Name	Required	Default
`device`	No	default
`follow`	No
`reopen`	No
`project`	Yes

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv0.4.0Oct 26, 2026
- addedInput schema / properties / reopen
```
Added value: +{
+  "default": true,
+  "type": "boolean"
+}
```
First observedv0.3.0Oct 3, 2026

TDQS

A4.4/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: a roughly one-second gap, automatic system-default following polled every few seconds, fallback to default when a device stops accepting audio, no gap under reopen=False, and an explicit list of what keeps running under device='none' (clock, queue, streams, recording, live_listen) with no restart. These are exactly the operational details 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 core action is front-loaded in the first clause, which is good, but the body is a dense run-on with nested parentheticals ('checked every few seconds; follow=False stops that') that is harder to scan than it needs to be. Every idea is relevant, yet the same ground is partly retrodden when device='none' is revisited at the end.

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 not be described, and the behavioral picture is unusually complete for a 0%-coverage, annotation-free mutation tool. The only missing pieces are the meaning of the required 'project' argument and what happens when a supplied device name matches nothing.

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 coverage is 0%, so the description must compensate, and it does for three of four parameters: device enumerates its accepted forms ('default', a name or partial name, an index, 'none') and its follow-up behavior, follow is explained via follow=False, and reopen=False is defined as changing follow only without reopening. The required 'project' parameter is never mentioned, which leaves one real gap.

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 clause states a specific verb and resource plus scope: move a running set to another audio output without stopping it, with what survives (timeline, queue, pre-mixed audio) spelled out. An agent can distinguish this from live_start/live_stop/phone_route without opening 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?

It gives concrete when-to-use conditions for each mode: 'default' after connecting a Bluetooth speaker, a partial name like 'JBL', 'none' to turn the room speaker off mid-set, reopen=False when you only want to change follow. It also names a non-tool equivalent (the phone page's Output switch), but it does not explicitly point at the closest sibling tools such as phone_route or live_stream to say which one wins.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server