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

ismail: agent DAW (MCP server)

Stream Visual

stream_visual

Configure the stream’s visualizer and frame in one call—select page, spectrum, waves, scope, or none; set colors, background/window capture, chat overlay, resolution, fps, and bitrate to avoid repeated encoder restarts.

Instructions

Set the stream's picture with raw numbers. While live this restarts the encoder: a 2-3 s blip on every site, so set everything in one call. mode: page (the visual page, drawn from the set's levels as stream_scene sets it: the one to change live with no blip), cqt (a piano-roll spectrum), spectrum (bars), waves, scope (a stereo vector scope) or none. colors: ['#rrggbb', '#rrggbb'] for spectrum and waves. background: '#rrggbb', or image: a still behind it, or window: the title of a window to capture (a page the agent draws, the VR stage mirror). area: [x, y, w, h] of the visualizer, fractions of the frame. chat_overlay: the newest chat line in the corner. width/height/fps: 1280x720 at 30 by default. video_kbps: 4500 (Twitch takes 6000 at most). encoder: auto (NVENC when the GPU has it), nvenc or x264. capture: how a window (or the page) is captured: auto (wgc where ffmpeg has it), wgc (Windows Graphics Capture: GPU-drawn pages such as the stage's WebGL, and a covered window, come through; the page draws on the GPU) or gdi (gdigrab: a GPU-drawn window comes out blank, so the page draws in software). A Chrome or Edge window is cropped to its web content. Look at the result with stream_look. An encoder that starts three times in a row with no picture stops the stream; stream_status says why and what to call next.

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

Input Schema

NameRequiredDescriptionDefault
fpsNo
areaNo
modeNo
imageNo
widthNo
colorsNo
heightNo
windowNo
captureNo
encoderNo
font_sizeNo
audio_kbpsNo
backgroundNo
text_colorNo
video_kbpsNo
chat_overlayNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.4.0

TDQS

A4.5/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 so well: it discloses the 2-3 s encoder blip on every site, the auto/NVENC/x264 fallback order, the Twitch 6000 kbps ceiling, the gdi blank-GPU-window trap, the Chrome/Edge content cropping, and the consecutive-failure abort. Only a few behavioural details (e.g. exact defaults for audio_kbps) are left unstated.

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?

Front-loads the most important constraint (encoder restart blip, batch everything into one call) before any parameter talk. It is dense semicolon-prose rather than a scannable list, but nearly every clause adds distinct information and nothing is padding.

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 explained, and the description covers the mutation risks, capture pitfalls and verification path appropriate for a 16-parameter live-streaming mutation. The only shortfall is the three undocumented parameters, mainly font_size and text_color.

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 explains 13 of 16 parameters: mode enumerations, colors format, background/image/window sources, area as fractional [x,y,w,h], chat_overlay, width/height/fps defaults, video_kbps ceiling, encoder options and capture semantics. It omits meaning for font_size, text_color and audio_kbps, leaving a small 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?

States a specific verb+resource ('Set the stream's picture with raw numbers') and then enumerates every mode (page, cqt, spectrum, waves, scope, none). It distinguishes itself from stream_scene (which drives the page's levels), from stream_look (used to inspect the result) and from stream_status (used when the encoder fails).

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

Usage Guidelines5/5

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

Gives explicit operational routing: set everything in one call because a change restarts the encoder, use page mode when changing live with no blip, and check the outcome with stream_look. It also names the failure path — three bad encoder starts stop the stream, and stream_status says why and what to call next.

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