Skip to main content
Glama

Music Studio

by io.github.linxule

Play Live Pattern

play-live-pattern
Read-onlyIdempotent

Live-code music patterns using TidalCycles mini-notation in JavaScript. Layer drums, synths, and bass with stack(). Choose from 72 drum machine banks, 128 GM instruments, built-in synths, and a full effects chain. Patterns play in a REPL the user can edit directly. Add .pianoroll() to a pattern to show a live piano-roll animation in the widget (or .punchcard()/.scope()/.spectrum() — use one visual per pattern). Use get-strudel-guide for genre templates, sound references, and advanced features like visualization, arrangement, and sample loading.

The Strudel REPL renders inline with an editable code editor, visualizations, and playback controls.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
bpmNoTempo in BPM (40-300). Converts to setcps() automatically.
codeYesStrudel pattern code. Uses TidalCycles mini-notation in JavaScript. Use stack() to layer drums, bass, and melody. Set tempo with setcps(bpm/60/4) or use the bpm parameter.
titleNoPattern title displayed in the widget header (e.g. 'Midnight Rain').
autoplayNoStart playing immediately (default: true). May require user click due to browser autoplay policy.

TDQS

A4.1/5.0
Behavior4/5

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

Annotations indicate safe, idempotent, read-only behavior. The description adds context: the REPL is editable directly, autoplay may require user click due to browser policy, and visualizations are available. This goes beyond the annotations without contradiction.

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 well-structured, front-loading the main purpose. It is detailed but not overly verbose; however, there is slight redundancy (REPL mentioned twice). It earns its length by covering key features.

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?

Given the complexity of live coding with a REPL and visualizations, the description covers core features, guides, and browser policies. No output schema exists, but the description explains what the REPL does. It is largely complete for agent use.

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%. The description adds minor context (e.g., bpm converts to setcps, code uses mini-notation, autoplay policy) but does not substantially enhance understanding beyond the schema. Baseline of 3 is appropriate.

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?

The description clearly states the verb ('live-code music patterns') and the resource (TidalCycles mini-notation via Strudel). It distinguishes from sibling tools like play-sheet-music and get-strudel-guide by mentioning specific capabilities like stack(), visualizations, and that it uses a REPL.

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?

The description mentions using get-strudel-guide for genre templates and advanced features, implying when not to use this tool. It provides clear context that this is for live coding patterns, but does not explicitly state exclusions relative to play-sheet-music.

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
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4/5.0
Disambiguation5/5

Each tool targets a distinct area: reference guides for different domains (ABC vs Strudel), live coding playback, sheet music playback, and documentation search. No overlap.

Naming Consistency5/5

All tool names follow a consistent verb_noun pattern in snake_case: get-music-guide, get-strudel-guide, play-live-pattern, play-sheet-music, search-music-docs.

Tool Count5/5

With 5 tools, the set is well-scoped for a music composition and live coding server. Each tool serves a clear purpose without bloat or thinness.

Completeness4/5

Core workflows are covered: reference, live coding, sheet music, and search. Minor gaps exist (e.g., no explicit project management or audio export), but the surface supports the server's purpose.

Resources