ismail: agent DAW (MCP server)

Overview Schema Source Related Servers Discussions Admin

Stream Scene

stream_scene

Set the visual page’s picture with raw numeric layer settings, updating instantly without a blip so music-reactive scenes change as the beat moves.

Instructions

Set the visual page's picture with raw numbers; it changes on the page (and on a stream in mode='page') at once, with no blip. Reach for it when you change what viewers see move with the music. layers: a list drawn in order, each {kind, x, y, w, h (fractions of the frame), ...}: bars {bands: [lo, hi], colors, gap, mirror, smooth, gain}: one bar per band; ring {x, y (centre), r, h (bar length), bands, thickness, spin (degrees per beat)}; pulse {x, y, r0, r1, drive, decay, fill}: a circle that swells with its drive; line {bands, thickness, fill}: the spectrum as a line; hits {tracks: {'': '#rrggbb'}, shape (circle, square, bar), decay}: a light per track that flashes on each of its notes; particles {x, y, count, speed, size, spawn (what bursts them: beat, track:, band:)}; text {text, x, y, size, align, drive}; grid {cols, rows, scroll (rows per beat), drive}. Every layer also takes color or colors (a gradient, '#rrggbb'), opacity, blend (source-over, lighter, screen, multiply, overlay), smooth (0-1) and gain. drive: level, beat, band:<0-15>, bands:- or track:. The 16 bands run log-spaced from 40 Hz to 16 kHz: 0-3 sub and bass, 4-7 low mids, 8-11 mids, 12-15 air. background: '#rrggbb' or a 2-3 colour gradient top to bottom. trails: 0-0.98, how long motion lingers. replace=False adds the layers on top of the current ones. A wrong setting is refused with what it takes.

Input Schema

Name	Required	Description	Default
`layers`	No
`trails`	No
`replace`	No
`background`	No

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Addedv0.4.0Oct 26, 2026

TDQS

A4/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 does disclose meaningful behavior: immediate no-blip updates, that replace=False adds layers rather than replacing them, and that invalid settings are refused with corrective information. It still does not fully cover mutation scope, permissions, or how this interacts with overall stream state.

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

Conciseness4/5

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

The description is long but appropriately structured for a complex layer schema, with purpose front-loaded and details organized by layer type. Some colloquial phrasing such as 'raw numbers' and 'no blip' could be tighter, but the length is largely earned.

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?

Given an empty-description schema, no annotations, and an output schema, the description is substantially complete for invocation: it documents all four parameters and the layer grammar. Minor gaps remain around sibling differentiation and the unexplained mode='page' reference.

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 description coverage is 0%, so the description must compensate fully. It does: layers, background, trails, and replace are all explained, including layer kinds, fields, drive syntax, band ranges, color/blend options, and additive vs. replacement behavior.

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 description states a specific verb and resource: setting the visual page's picture with layer data, updating live without a blip. It does not explicitly distinguish itself from sibling stream tools such as stream_visual or stream_page, and 'raw numbers' is slightly vague, but the core purpose is clear.

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?

It gives a use case: 'Reach for it when you change what viewers see move with the music.' However, it does not name alternatives or state when not to use this tool, and the referenced mode='page' is not a parameter in the schema, leaving some routing ambiguity.

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

Deploy Server