Skip to main content
Glama
newsbubbles

ismail: agent DAW (MCP server)

Stage Perform

stage_perform

Control a live performance Follow: start, stop, and rotate mic clips, add timestamped markers, query state, and end the session, with word-timed transcripts returned.

Instructions

Your hand on a performance (page command: perform). A Follow is a performance: while someone follows the person no gesture acts (pokes still press panels), your speech is shown and not spoken (stage_say aloud=True speaks), and the mic records from the first moment in clips on the Follow's clock (seconds since it began). action: 'state' (default): {performing, perf, person, seconds, mic, clip, clips, markers, take}; 'stop': end the whole performance: the Follow, and a take recording with it (the person can too: both thumbs down held 1.5 s, saying "stop the performance", or Stop on the Follow panel, which opens however the Follow began); 'stop_clip': end the clip now so it is transcribed (the person goes on; the mic waits for start_clip); 'start_clip': record the next clip (turns the mic back on); 'next_clip': stop_clip then start_clip in one step (read one part while recording the next); 'mic_off': end the clip and leave the mic off (start_clip turns it on); 'mark': a marker with label= at this moment on the Follow clock. Clips also cut themselves at the first pause after 6 s, or at 25 s, so the words arrive while they go on: each perform_clip with words also reaches stage_listen. A stopped clip arrives as event perform_clip {perf, clip, at, seconds, text, words: [[word, start, end]]} with word times on the Follow clock, snapped onto the measured voice; stage_performance reads a whole performance. The Follow panel has Mic off / Mic on for the person. Errors: nobody follows the person; the mic is not allowed. Emits: perform_clip_start, perform_clip_stop, perform_mic, perform_mark, perform_stop_asked, perform_stop (and from the server perform_clip_in, perform_clip).

Input Schema

NameRequiredDescriptionDefault
labelNo
sceneYes
actionNostate

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.4.0

TDQS

A3.8/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 behavioral burden and does so well: it explains what stop destroys, how the mic and clips behave, automatic clip cutting at 6 s/25 s, transcription routing to stage_listen, emitted events, and error conditions. These are exactly the side effects and constraints an agent needs before invoking the tool.

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 purpose and action semantics are front-loaded, and most sentences carry useful behavioral detail. However, the description is a dense block with embedded semicolon-separated actions, making it harder to scan than a more structured presentation would be.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/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-value detail is less necessary, and the description covers behavior, events, and errors extensively. The critical gap is the required scene parameter, which is undefined in both schema and description, so the definition is not fully complete for correct invocation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0%, so the description must explain all three parameters, but it only thoroughly documents action values and mentions label briefly in the mark action. The required scene parameter is never explained, leaving the agent without guidance on what identifier or object to supply.

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 role: controlling a live performance and its mic/clip workflow, with the action list clarifying what the tool does. It distinguishes itself from stage_performance ('reads a whole performance') and stage_say ('aloud=True speaks'), though the domain-specific 'Follow' framing is not fully self-explanatory.

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 detailed per-action guidance for state, stop, stop_clip, start_clip, next_clip, mic_off, and mark, including defaults and sequencing. It does not comprehensively route the agent between this tool and all nearby siblings such as stage_start, stage_stop, stage_status, or stage_events, but the action-level guidance is strong.

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