Skip to main content
Glama

Music Studio

by io.github.linxule
OverviewDiscussionsAdmin

Update Live Session

update-session

Only for a live session. Swaps new code into the session's player while the music keeps playing. Send the WHOLE pattern, as for play-live-pattern. It lands on the next bar (quantize 1, the default), the next multiple of n bars, or at once (0): set quantize to your phrase length (8-bar phrase → 8). If the player answers within a few seconds, the result says whether it ran the code, or its error. To change a piece's remember() state, ship a merge, not a new start value (get-strudel-guide topic 'interactive').

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
codeYesThe complete new Strudel pattern (same rules as play-live-pattern's code).
sessionYesThe session id from play-live-pattern's result (16 lowercase letters/digits).
quantizeNoLand on the next multiple of this many cycles (bars). 1 = next bar (default), 4/8 = phrase, 0 = now.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.8/5.0
Behavior5/5

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

Annotations declare non-readonly, non-destructive, non-idempotent, but the description adds real behavior: playback continues uninterrupted, code lands on a quantized boundary, and the result may report success or a code error only if the player responds within a few seconds. It also discloses the merge semantics needed to change remember() 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?

Five dense sentences, front-loaded with the live-session constraint and the core action; every sentence carries operational information. Slightly long sentences, but nothing is wasted.

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

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, the description still explains what the result reports and its timing caveat, plus session-id provenance from play-live-pattern. An agent has everything needed to call this correctly in the live-session workflow.

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 100%, so baseline is 3, but the description adds a heuristic the schema lacks: set quantize to the phrase length (8-bar phrase → 8) and that 1 is the next bar. It also reinforces that code must be the WHOLE pattern, matching play-live-pattern's rules.

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 and resource: it swaps new code into a live session's player without stopping playback. The opening constraint 'Only for a live session' immediately separates it from play-live-pattern, which starts a session rather than updating one.

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 preconditions (live session only), routes the agent to play-live-pattern for the code rules, specifies how to pick quantize (phrase length, 0 for immediate), and names get-strudel-guide topic 'interactive' for the merge-not-new-start case. Both alternatives and when-not conditions are covered.

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

All Music Studio toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources