Skip to main content
Glama

Music Studio

by io.github.linxule
OverviewDiscussionsAdmin

Strudel Reference Guide

get-strudel-guide
Read-onlyIdempotent

Reference and recipes for Strudel live coding. Music: genres (complete templates: techno, house, dnb, ambient, jazz, lofi, synthwave), mini-notation, sounds (synths, 71 drum banks, 128 GM instruments, vcsl samples), effects, patterns, tips (tempo, common mistakes), advanced (samples, wavetables, signals, chord voicings). Visuals: visuals (draw methods, presets, themes), hydra (shader backgrounds, H(pattern), the audio-reactive a.fft). Optional modules — the code is real browser JavaScript: stage (your own canvases, onFrame/onEvent/onTap, say), film (scenes on bars, text, narration), interactive (taps into notes, faders/pads/xy, tilt/mic, remember() for controls you draw, live sessions), craft (what makes a piece land), debugging (what the player reports back), gallery (complete pieces; fetch one with piece).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pieceNoWith topic 'gallery': the complete code of one piece (the index lists them).
topicYesReference topic. Start with 'genres' for working templates, 'sounds' for instruments, 'visuals' for draw methods and presets, 'hydra' for shader backgrounds, 'advanced' for sample loading. For a music video or film: 'craft', 'stage', 'film', then gallery piece 'first-light'. For taps, controls, a drawn grid or a jam: 'interactive' alone (take only the sections you need), then gallery piece 'weather-machine' or 'trade-a-beat'.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / piece / enum
      Previous value: -[
-  "first-light",
-  "duet",
-  "petri-dish",
-  "lossy-terminal",
-  "signal-corruption",
-  "weather-machine",
-  "two-decks",
-  "trade-a-beat"
-]New value: +[
+  "first-light",
+  "duet",
+  "petri-dish",
+  "lossy-terminal",
+  "signal-corruption",
+  "weather-machine",
+  "two-decks",
+  "trade-a-beat",
+  "still-water",
+  "lullaby"
+]
  2. Changed1 schema field changed
    • changedInput schema / properties / topic / description
      Previous value: -"Reference topic. Start with 'genres' for working templates, 'sounds' for instruments, 'visuals' for draw methods and presets, 'hydra' for shader backgrounds, 'advanced' for sample loading. For a music video, film or interactive piece: 'craft', then 'stage', 'film' or 'interactive', and a worked example from 'gallery'."New value: +"Reference topic. Start with 'genres' for working templates, 'sounds' for instruments, 'visuals' for draw methods and presets, 'hydra' for shader backgrounds, 'advanced' for sample loading. For a music video or film: 'craft', 'stage', 'film', then gallery piece 'first-light'. For taps, controls, a drawn grid or a jam: 'interactive' alone (take only the sections you need), then gallery piece 'weather-machine' or 'trade-a-beat'."
  3. Changed1 schema field changed
    • changedInput schema / properties / piece / enum
      Previous value: -[
-  "first-light",
-  "duet",
-  "petri-dish",
-  "lossy-terminal",
-  "signal-corruption",
-  "weather-machine",
-  "two-decks"
-]New value: +[
+  "first-light",
+  "duet",
+  "petri-dish",
+  "lossy-terminal",
+  "signal-corruption",
+  "weather-machine",
+  "two-decks",
+  "trade-a-beat"
+]
  4. Changed1 schema field changed
    • changedInput schema / properties / piece / enum
      Previous value: -[
-  "first-light",
-  "duet",
-  "petri-dish",
-  "lossy-terminal",
-  "signal-corruption",
-  "weather-machine"
-]New value: +[
+  "first-light",
+  "duet",
+  "petri-dish",
+  "lossy-terminal",
+  "signal-corruption",
+  "weather-machine",
+  "two-decks"
+]
  5. Changed1 schema field changed
    • changedInput schema / properties / piece / enum
      Previous value: -[
-  "first-light",
-  "duet",
-  "petri-dish",
-  "lossy-terminal",
-  "signal-corruption"
-]New value: +[
+  "first-light",
+  "duet",
+  "petri-dish",
+  "lossy-terminal",
+  "signal-corruption",
+  "weather-machine"
+]
  6. Changed3 schema fields changed
    • addedInput schema / properties / piece
      Added value: +{
+  "description": "With topic 'gallery': the complete code of one piece (the index lists them).",
+  "enum": [
+    "first-light",
+    "duet",
+    "petri-dish",
+    "lossy-terminal",
+    "signal-corruption"
+  ],
+  "type": "string"
+}
    • changedInput schema / properties / topic / description
      Previous value: -"Reference topic. Start with 'genres' for working templates, 'sounds' for instruments, 'visuals' for draw methods and presets, 'hydra' for shader backgrounds, 'advanced' for sample loading."New value: +"Reference topic. Start with 'genres' for working templates, 'sounds' for instruments, 'visuals' for draw methods and presets, 'hydra' for shader backgrounds, 'advanced' for sample loading. For a music video, film or interactive piece: 'craft', then 'stage', 'film' or 'interactive', and a worked example from 'gallery'."
    • changedInput schema / properties / topic / enum
      Previous value: -[
-  "mini-notation",
-  "sounds",
-  "effects",
-  "patterns",
-  "genres",
-  "tips",
-  "visuals",
-  "hydra",
-  "advanced"
-]New value: +[
+  "mini-notation",
+  "sounds",
+  "effects",
+  "patterns",
+  "genres",
+  "tips",
+  "visuals",
+  "hydra",
+  "advanced",
+  "stage",
+  "film",
+  "interactive",
+  "craft",
+  "debugging",
+  "gallery"
+]
  7. Changed2 schema fields changed
    • changedInput schema / properties / topic / description
      Previous value: -"Reference topic. Start with 'genres' for working templates, 'sounds' for instruments, 'visuals' for animations and Hydra backgrounds, 'advanced' for sample loading."New value: +"Reference topic. Start with 'genres' for working templates, 'sounds' for instruments, 'visuals' for draw methods and presets, 'hydra' for shader backgrounds, 'advanced' for sample loading."
    • changedInput schema / properties / topic / enum
      Previous value: -[
-  "mini-notation",
-  "sounds",
-  "effects",
-  "patterns",
-  "genres",
-  "tips",
-  "visuals",
-  "advanced"
-]New value: +[
+  "mini-notation",
+  "sounds",
+  "effects",
+  "patterns",
+  "genres",
+  "tips",
+  "visuals",
+  "hydra",
+  "advanced"
+]
  8. Changed2 schema fields changed
    • changedInput schema / properties / topic / description
      Previous value: -"Reference topic. Start with 'genres' for working templates, 'sounds' for instruments, 'advanced' for visualization and sample loading."New value: +"Reference topic. Start with 'genres' for working templates, 'sounds' for instruments, 'visuals' for animations and Hydra backgrounds, 'advanced' for sample loading."
    • changedInput schema / properties / topic / enum
      Previous value: -[
-  "mini-notation",
-  "sounds",
-  "effects",
-  "patterns",
-  "genres",
-  "tips",
-  "advanced"
-]New value: +[
+  "mini-notation",
+  "sounds",
+  "effects",
+  "patterns",
+  "genres",
+  "tips",
+  "visuals",
+  "advanced"
+]
  9. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered. The description adds that the returned material is 'real browser JavaScript' with runnable templates and that gallery pieces are complete code, which is useful context about output nature, but it says nothing about response size, format, or truncation for a guide with 15 topics.

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 is front-loaded in the first clause, and every parenthetical enumerates content that maps to a real enum value rather than being filler. The nested parentheticals get dense, but no sentence is redundant with the others.

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?

For a read-only reference tool with 100% schema coverage and no output schema, the description tells the agent what each of the 15 topics yields, which is the information needed to pick a topic. Only the return format (markdown? code blocks?) is unstated, a minor gap for a documentation tool.

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

Parameters3/5

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

Schema description coverage is 100% and both parameters are enums with their own schema descriptions, so the schema already carries the semantics. The description reinforces the `piece` linkage to the gallery topic ('gallery (complete pieces; fetch one with `piece`)') but adds no syntax or format detail beyond the schema — the baseline 3 applies.

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 line states a specific resource ('Reference and recipes for Strudel live coding') and the body enumerates exactly what the guide covers (mini-notation, sounds, effects, visuals, hydra, stage, film, etc.), so the agent knows this is a documentation/content-retrieval tool. It never distinguishes itself from the sibling get-music-guide or search-music-docs, which is the only thing keeping it from a 5.

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?

The description implies usage by listing topics and noting 'fetch one with `piece`', but never states when to call this instead of get-music-guide or search-music-docs. The genuinely useful routing advice ('Start with genres...', 'For a music video or film: craft, stage, film') lives in the topic schema description, not in the tool description, so the description itself only implies the workflow.

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