Skip to main content
Glama
williamzujkowski

Strudel MCP Server

set_tempo

Adjust the tempo in beats per minute (BPM) for music patterns in Strudel.cc, enabling precise control over timing during AI-powered music generation and live coding sessions.

Instructions

Set BPM

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
bpmYesTempo in BPM

Implementation Reference

  • The executeTool switch case that implements the set_tempo tool: validates the bpm input, prepends a setcpm(bpm) line to the current pattern, writes the updated pattern to the editor, and returns a confirmation message.
    case 'set_tempo':
      InputValidator.validateBPM(args.bpm);
      const currentTempo = await this.getCurrentPatternSafe();
      const withTempo = `setcpm(${args.bpm})\n${currentTempo}`;
      await this.writePatternSafe(withTempo);
      return `Set tempo to ${args.bpm} BPM`;
  • The tool definition in getTools() including name, description, and input schema requiring a numeric bpm parameter. This is used for both listing tools and validation.
    {
      name: 'set_tempo',
      description: 'Set BPM',
      inputSchema: {
        type: 'object',
        properties: {
          bpm: { type: 'number', description: 'Tempo in BPM' }
        },
        required: ['bpm']
      }
  • Array in requiresInitialization() helper function that includes 'set_tempo' among tools requiring browser initialization before execution.
    const toolsRequiringInit = [
      'write', 'append', 'insert', 'replace', 'play', 'pause', 'stop',
      'clear', 'get_pattern', 'analyze', 'analyze_spectrum', 'analyze_rhythm',
      'transpose', 'reverse', 'stretch', 'humanize', 'generate_variation',
      'add_effect', 'add_swing', 'set_tempo', 'save', 'undo', 'redo',
      'validate_pattern_runtime'
    ];
Behavior1/5

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

No annotations are provided, so the description carries full burden. 'Set BPM' implies a write/mutation operation but doesn't disclose any behavioral traits: it doesn't specify if this changes global settings, affects current playback, requires specific permissions, has side effects, or what happens on success/failure.

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 description is extremely concise at two words, with zero wasted text. It's front-loaded with the core action, though this brevity comes at the cost of completeness.

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?

Given no annotations, no output schema, and a mutation tool with behavioral implications, the description is incomplete. It doesn't explain what 'setting' entails, the scope of the change, or what to expect after invocation, leaving significant gaps for the agent.

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%, with the single parameter 'bpm' documented as 'Tempo in BPM'. The description adds no additional meaning beyond this, so it meets the baseline of 3 where the schema does the heavy lifting.

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

Purpose2/5

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

The description 'Set BPM' restates the tool name 'set_tempo' in slightly different wording (BPM vs tempo), making it tautological. It doesn't specify what resource or system the tempo is being set for, nor does it distinguish from sibling tools like 'detect_tempo' or 'generate_pattern' that might involve tempo manipulation.

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

Usage Guidelines1/5

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

No guidance is provided on when to use this tool versus alternatives. It doesn't mention prerequisites, context (e.g., during playback, composition), or exclusions, leaving the agent to guess based on the name alone.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/williamzujkowski/strudel-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server