Skip to main content
Glama
williamzujkowski

Strudel MCP Server

play

Start playing musical patterns in Strudel for AI-powered music generation and live coding. Control browser automation to create, analyze, and store TidalCycles patterns.

Instructions

Start playing pattern

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Registration of the 'play' tool including name, description, and input schema in the tools list returned by getTools()
      name: 'play',
      description: 'Start playing pattern',
      inputSchema: { type: 'object', properties: {} }
    },
  • MCP tool handler in executeTool switch statement - delegates to StrudelController.play()
    case 'play':
      return await this.controller.play();
  • Core implementation of play functionality: sends keyboard shortcut to Strudel browser to start playback and updates internal state
    async play(): Promise<string> {
      if (!this._page) throw new Error('Browser not initialized. Run init tool first.');
    
      // Always use keyboard shortcut for speed
      await this._page.keyboard.press('ControlOrMeta+Enter');
    
      // Reduced wait time
      await this._page.waitForTimeout(100);
    
      this.isPlaying = true;
      return 'Playing';
    }
Behavior2/5

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

No annotations are provided, so the description carries full burden. 'Start playing pattern' implies an action that initiates playback, but it doesn't disclose behavioral traits such as whether playback is immediate, if it requires specific permissions, what happens if no pattern is loaded, or if it affects other tools (e.g., interacting with 'pause' or 'stop'). This leaves significant gaps in understanding the tool's behavior.

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 'Start playing pattern' is extremely concise with only three words, front-loading the core action. Every word earns its place by conveying the essential purpose without any wasted text. It's appropriately sized for a simple tool with no parameters.

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 the tool's simplicity (0 parameters, no annotations, no output schema), the description is incomplete. It doesn't explain what 'pattern' means in this context, how playback interacts with other tools, or what the expected outcome is. For a playback control tool among many siblings, more context is needed to ensure proper usage.

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

Parameters4/5

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

The tool has 0 parameters with 100% schema description coverage, so the schema fully documents the lack of inputs. The description doesn't add parameter semantics, but this is acceptable since there are no parameters to explain. A baseline of 4 is appropriate as the description doesn't need to compensate for any parameter gaps.

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 'Start playing pattern' states a clear action (start playing) but is vague about what resource is being played (pattern). It doesn't differentiate from sibling tools like 'pause', 'stop', or 'set_tempo' which also relate to playback control. The purpose is understandable but lacks specificity about what 'pattern' refers to in this context.

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?

The description provides no guidance on when to use this tool versus alternatives like 'pause', 'stop', or 'set_tempo'. It doesn't mention prerequisites (e.g., whether a pattern must be loaded first) or exclusions. The agent must infer usage from the tool name alone, which is insufficient for informed selection.

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