Skip to main content
Glama
Sign In
SuperCollider OSC MCP

SuperCollider OSC MCP

by Tok
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

create_generative_rhythm

Generate evolving drum patterns that mutate bar by bar across minimal, techno, glitch, jazz, or ambient styles, with controls for tempo, intensity, duration, and effects.

Instructions

Play drums that keep mutating bar by bar (minimal, techno, glitch, jazz or ambient).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "create_generative_rhythm"
  }
}

Input Schema

NameRequiredDescriptionDefault
seedNoRandom seed for a reproducible result; omit for a new one
styleNominimal
tempoNoBeats per minute
volumeNoLoudness, 0..1
effectsNoOptional effect chain
durationNoSeconds
intensityNoHow busy and how changeable

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.1

TDQS

B3.3/5.0
Behavior3/5

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

The description adds useful behavioral context beyond the annotations by disclosing that the rhythm mutates bar by bar and naming the supported styles. However, it does not describe playback behavior, duration, reproducibility via seed, or how effects are applied; annotations already cover the safety profile.

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?

The definition is a single front-loaded sentence with no wasted words. It efficiently communicates the core action, generative behavior, and style range.

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

Completeness3/5

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

The tool has seven parameters and an output schema, and the input schema already describes parameters well. The description covers the essence of the tool but is thin on when to choose it over sibling drum/sequence tools and lacks behavioral detail for a generative audio 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 high (86%), so the schema already documents most parameters including tempo, duration, intensity, seed, and effects. The description only repeats the style enum values and adds no further meaning about how parameters interact or what values produce what musical result.

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 description states a specific verb and resource ('Play drums') and adds the key distinguishing behavior ('keep mutating bar by bar') plus genre styles. It is clear what the tool does, though it does not explicitly contrast with siblings like create_drum_pattern or create_sequence.

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 explicit guidance on when to use this tool versus alternatives such as create_drum_pattern or create_sequence. The generative/mutating nature implies a use case, but the agent must infer it without any stated exclusions or conditions.

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