Skip to main content
Glama
williamzujkowski

Strudel MCP Server

add_effect

Apply audio effects to music patterns in Strudel MCP Server by specifying effect names and parameters for sound manipulation during AI-powered music generation.

Instructions

Add effect to pattern

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
effectYesEffect name
paramsNoEffect parameters

Implementation Reference

  • Handler for 'add_effect' tool: validates inputs, appends effect syntax (e.g., .effect(params)) to current pattern, writes it back to Strudel editor, returns confirmation.
    case 'add_effect':
      InputValidator.validateStringLength(args.effect, 'effect', 100, false);
      if (args.params) {
        InputValidator.validateStringLength(args.params, 'params', 1000, true);
      }
      const currentEffect = await this.getCurrentPatternSafe();
      const withEffect = args.params
        ? currentEffect + `.${args.effect}(${args.params})`
        : currentEffect + `.${args.effect}()`;
      await this.writePatternSafe(withEffect);
      return `Added ${args.effect} effect`;
  • Schema definition for 'add_effect' tool in the tools list returned by getTools(), used for MCP tool listing and input validation.
      name: 'add_effect',
      description: 'Add effect to pattern',
      inputSchema: {
        type: 'object',
        properties: {
          effect: { type: 'string', description: 'Effect name' },
          params: { type: 'string', description: 'Effect parameters' }
        },
        required: ['effect']
      }
    },
  • Registration of tool list handler; 'add_effect' is included in getTools() array.
    this.server.setRequestHandler(ListToolsRequestSchema, async () => ({
      tools: this.getTools()
    }));
  • Helper method that identifies 'add_effect' as requiring browser initialization before execution.
    private requiresInitialization(toolName: string): boolean {
      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'
      ];
      
      const toolsRequiringWrite = [
        'generate_pattern', 'generate_drums', 'generate_bassline', 'generate_melody',
        'generate_chord_progression', 'generate_euclidean', 'generate_polyrhythm',
        'generate_fill'
      ];
      
      return toolsRequiringInit.includes(toolName) || toolsRequiringWrite.includes(toolName);
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 for behavioral disclosure. 'Add effect to pattern' implies a mutation operation, but it doesn't specify whether this is destructive, requires specific permissions, has side effects, or what happens on success/failure. For a mutation tool with zero annotation coverage, this is completely inadequate.

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 just four words. It's front-loaded with the core action and doesn't waste words. While under-specified, it earns full marks for conciseness as every word contributes directly to the stated purpose.

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

Completeness1/5

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

Given this is a mutation tool with no annotations, no output schema, and 2 parameters, the description is severely incomplete. It doesn't explain what happens after adding the effect, what the pattern is, or any behavioral context. The agent would struggle to use this tool correctly without significant guesswork.

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?

The input schema has 100% description coverage, with both parameters ('effect' and 'params') documented in the schema. The description adds no additional meaning about what constitutes valid effects, parameter formats, or examples. With high schema coverage, the baseline score of 3 is appropriate as 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 'Add effect to pattern' restates the tool name 'add_effect' without providing additional specificity. It doesn't clarify what type of effect, what kind of pattern, or how this differs from sibling tools like 'remove_effect' or 'apply_scale'. This is a tautology that offers minimal value beyond the name itself.

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?

There is no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites (e.g., needing an existing pattern), when not to use it, or how it relates to sibling tools like 'remove_effect' or 'generate_pattern'. The description provides zero contextual usage information.

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