Skip to main content
Glama

Music Studio

by io.github.linxule

Play Sheet Music

play-sheet-music
Read-onlyIdempotent

Compose and play sheet music with visual notation, multi-instrument audio, and style presets. Write ABC notation for melodies, arrangements, harmonized pieces, or well-known tunes. Add a style (rock, jazz, bossa, waltz, folk...) for automatic drums, bass, and chord accompaniment. Returns a parse-status confirmation and renders the player; it does not return raw audio. Use get-music-guide for genre templates, instrument lists, and ABC syntax reference.

The music player renders inline with interactive playback controls.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
styleNoAccompaniment style. Adds drums, bass, and chord patterns automatically. Your ABC needs chord symbols ("C", "Am") for accompaniment to work. Options: rock, jazz, bossa, waltz, march, reggae, folk, classical.
swingNoSwing percentage (0-100). 0=straight, 33=light swing, 66=heavy swing. Great for jazz and blues.
tempoNoTempo in BPM (40-240). Overrides Q: in ABC notation.
titleNoPiece title (overrides T: in ABC). Displayed in the widget header.
transposeNoTranspose by semitones (-12 to 12). Positive=higher, negative=lower.
instrumentNoDefault instrument (e.g. 'Flute', 'Cello', 'Acoustic Grand Piano', 'Alto Sax'). Use get-music-guide with topic 'instruments' for the full list.
abcNotationNoABC notation string. Include chord symbols ("C", "Am7") above notes for auto-accompaniment with style presets.X:1 T:Twinkle, Twinkle Little Star M:4/4 L:1/4 K:C C C G G | A A G2 | F F E E | D D C2 | G G F F | E E D2 | G G F F | E E D2 | C C G G | A A G2 | F F E E | D D C2 |

TDQS

A4.5/5.0
Behavior4/5

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

Description adds behavioral context beyond annotations: it returns parse-status confirmation and renders a player with interactive playback controls, not raw audio. Annotations already declare readOnlyHint=true and idempotentHint=true, so no contradiction.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Concise and front-loaded with key purpose. No wasted sentences; essential caveats included efficiently.

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?

Given 7 parameters, no output schema, and good annotations, the description is complete. It explains the tool's output, behavior, and directs to sibling tools for additional info.

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 coverage is 100% with detailed descriptions for all 7 parameters. The description does not add meaning beyond what the schema provides, so 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 tool composes and plays sheet music with visual notation, audio, and style presets. It distinguishes from siblings like get-music-guide by specifying its direct functionality.

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?

Explicitly states when to use (composing sheet music) and when not (does not return raw audio). Directs users to get-music-guide for genre templates and syntax reference.

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