Skip to main content
Glama
Strudel MCP Server

Strudel MCP Server

audio_capture

Records audio output from a live Strudel session: start or stop streaming capture, or sample a fixed-duration window, and return base64-encoded audio.

Instructions

Record audio output from the live Strudel session. action=start begins streaming capture (optional format webm/opus, default webm). action=stop ends the stream and returns base64-encoded audio. action=sample captures a fixed-duration window in one call (100-60000ms, default 5000ms). Example: audio_capture({ action: "sample", duration: 3000 }). Audio must be playing for capture to record meaningful data. For MIDI export use export_midi; for runtime diagnostics use diagnostics. Each session has its own recorder, so captures in different sessions do not interfere (#180).

Input Schema

NameRequiredDescriptionDefault
actionYesCapture action
formatNoaction=start: audio format (default webm)
durationNoaction=sample: duration ms (100-60000, default 5000)
session_idNoOptional session ID (#108). Routes the capture to the named session, which has its own recorder — concurrent captures across sessions are safe (#180).
maxDurationNoaction=start: stop the recorder automatically after this many ms. Defaults to 600000 (ten minutes); the recording so far is kept and returned by a later stop.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv4.1.1
    • changedInput schema / properties / maxDuration / description
      Previous value: -"action=start: maximum capture duration ms"New value: +"action=start: stop the recorder automatically after this many ms. Defaults to 600000 (ten minutes); the recording so far is kept and returned by a later stop."
    • changedInput schema / properties / session_id / description
      Previous value: -"Optional session ID (#108). Routes page reference to the named session. Note: AudioCaptureService is currently server-wide — concurrent captures across sessions will conflict."New value: +"Optional session ID (#108). Routes the capture to the named session, which has its own recorder — concurrent captures across sessions are safe (#180)."
  2. Addedv4.0.0

TDQS

A4/5.0
Behavior4/5

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

With no annotations, the description itself discloses the streaming start/stop lifecycle, base64 output on stop, fixed-window sampling, the playback prerequisite, and per-session recorder isolation. This is strong operational context, although raw base64 versus a data URI and behavior for invalid recorder states are not specified.

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 front-loaded and dense with usable operational detail, including a compact example. Repeated defaults and ranges already present in the schema, plus internal issue markers such as (#180), add slight noise.

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?

Together with the fully described schema, it covers the three invocation modes, output encoding, preconditions, limits and defaults, and concurrent-session behavior sufficiently for most calls. The base64 statement partly compensates for the absent output schema, but export_audio selection guidance and recorder-state or error behavior remain uncovered.

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?

Although schema coverage is 100%, the action schema only says "Capture action"; the description adds the meaningful start/stop/sample workflow and a concrete sample invocation. Much of the format, duration, and session detail repeats the schema, and maxDuration is left entirely to the schema, so this is above baseline rather than exhaustive.

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, resource, and live-session scope, while the action breakdown makes the tool's role clear. It distinguishes the tool from export_midi and diagnostics but not from export_audio, the closest sibling for audio-related selection.

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 guidance for start, stop, and sample, states that audio must be playing, and routes MIDI export and runtime diagnostics to named alternatives. It does not explain when live capture is preferable to export_audio, leaving the most likely sibling-selection ambiguity unresolved.

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