Skip to main content
Glama
Sign In
SuperCollider OSC MCP

SuperCollider OSC MCP

by Tok
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

create_sequence

Play a melody note by note from a defined note pattern, with tempo, synth, volume, and effects controls.

Instructions

Play a melody you write out note by note.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "pattern": "<pattern>"
    },
    "name": "create_sequence"
  }
}

Input Schema

NameRequiredDescriptionDefault
synthNosine
tempoNoBeats per minute
volumeNoLoudness, 0..1
effectsNoOptional effect chain
patternYesNotes separated by spaces or dashes, e.g. 'C4 E4 G4_ G4_ . C5+'. '_' halves a note, '+' doubles it, ':1.5' sets the length in beats, '.' is a rest
repeatsNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.1

TDQS

C2.4/5.0
Behavior2/5

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

Annotations already establish the safety profile (readOnlyHint=false, destructiveHint=false, openWorldHint=false). Beyond the bare word 'Play', the description adds nothing: it does not say how long playback lasts, whether the call blocks, what stop_all does to it, or what limits apply to overlapping audio.

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?

It is one short, front-loaded sentence with no padding. Its brevity is efficient, though it borders on under-specification rather than crispness.

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

Completeness2/5

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

The tool has six parameters, including a nested effect chain and a flexible note syntax, and sits among many audio-creation siblings; one sentence covers none of that. The existence of an output schema excuses explaining return values, but not the missing differentiation and behavioral context.

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

Parameters2/5

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

Schema coverage is mid-range at 67%, and the description mentions no parameter at all; even the core 'pattern' argument is only hinted at by the phrase 'note by note', while synth, tempo, volume, effects, and repeats get no explanation of how they shape the output. The rich pattern mini-language is documented in the schema, so the description adds nothing there either.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description supplies a specific verb and resource ('Play a melody'), but it is nearly indistinguishable from the sibling play_melody, and it never makes clear how writing notes here differs from the other playback tools. An agent could pick either tool at random.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no guidance on when to use create_sequence rather than play_melody, play_synth, or create_chord_progression, and no note on prerequisites such as whether concurrent playback is possible. Usage can only be inferred from the name.

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

Deploy Server

Other Tools