Create complex rhythmic patterns by layering multiple simultaneous rhythms with different sounds. Specify sounds and pattern numbers to generate polyrhythms for algorithmic music composition.
Generate polyrhythm
| Name | Required | Description | Default |
|---|---|---|---|
| sounds | Yes | Sounds to use | |
| patterns | Yes | Pattern numbers |
Changes observed during successful MCP inspections.
v2.2.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations and the description gives no behavioral details, such as side effects, return values, or whether it modifies existing state.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Extremely short but lacks substance; under-specification rather than concise clarity.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the complexity of polyrhythm generation and no output schema, the description fails to provide essential context about functionality or results.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 100% with minimal descriptions ('Sounds to use', 'Pattern numbers'), but the tool description adds no further meaning or relationship between parameters.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
Description 'Generate polyrhythm' is a tautology repeating the tool name. It does not indicate what a polyrhythm is or differentiate from siblings like generate_drums or generate_pattern.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
No information on when to use this tool versus alternatives; no prerequisites or context provided.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.