Skip to main content
Glama
williamzujkowski

Strudel MCP Server

generate_fill

Create drum fills for music patterns by specifying style and duration. This tool helps musicians and producers add rhythmic variations to their compositions using Strudel MCP Server's music generation capabilities.

Instructions

Generate drum fill

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
styleYesFill style
barsNoNumber of bars

Implementation Reference

  • Registration of the 'generate_fill' tool including name, description, and input schema.
    {
      name: 'generate_fill',
      description: 'Generate drum fill',
      inputSchema: {
        type: 'object',
        properties: {
          style: { type: 'string', description: 'Fill style' },
          bars: { type: 'number', description: 'Number of bars' }
        },
        required: ['style']
      }
    },
  • Input schema definition for the generate_fill tool specifying style (required) and optional bars.
    inputSchema: {
      type: 'object',
      properties: {
        style: { type: 'string', description: 'Fill style' },
        bars: { type: 'number', description: 'Number of bars' }
      },
      required: ['style']
  • Main handler logic for generate_fill: validates args, generates fill via PatternGenerator, appends to current pattern, writes it, and returns confirmation.
    case 'generate_fill':
      InputValidator.validateStringLength(args.style, 'style', 100, false);
      if (args.bars !== undefined) {
        InputValidator.validatePositiveInteger(args.bars, 'bars');
      }
      const fill = this.generator.generateFill(args.style, args.bars || 1);
      const currentFill = await this.getCurrentPatternSafe();
      const newFillPattern = currentFill ? currentFill + '\n' + fill : fill;
      await this.writePatternSafe(newFillPattern);
      return `Generated ${args.bars || 1} bar fill`;
  • Implementation of generateFill method in PatternGenerator service, providing predefined Strudel patterns for different drum fill styles.
    generateFill(style: string, bars: number = 1): string {
      const fills: Record<string, string> = {
        techno: `s("bd*8, cp*4").fast(${bars})`,
        house: `s("bd*4, cp*2, hh*16").fast(${bars})`,
        dnb: `s("bd*8, sn*8").fast(${bars * 2})`,
        trap: `s("bd*4, hh*32").fast(${bars})`,
        breakbeat: `s("bd cp bd cp, hh*8").iter(4).fast(${bars})`
      };
      
      return fills[style] || fills.techno;
    }
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. 'Generate drum fill' implies a creation operation but reveals nothing about permissions, side effects, output format, rate limits, or error conditions. For a tool with no annotation coverage, this is a significant gap in transparency.

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 language. It's front-loaded with the core action and resource, making it easy to parse quickly. Every word earns its place by communicating the essential function.

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 generation tool with potential complexity, the description is incomplete. It doesn't explain what a drum fill is, what the output looks like (audio, notation, pattern), or any behavioral traits. For a tool in a music generation context with many siblings, more context is needed.

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 both parameters ('style' and 'bars') documented in the schema. The description adds no additional meaning about parameters beyond what the schema provides (e.g., what 'style' entails, typical 'bars' values). Baseline 3 is appropriate when the schema does the heavy lifting.

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 'Generate drum fill' clearly states the action (generate) and resource (drum fill), providing a basic purpose. However, it doesn't differentiate from sibling tools like 'generate_drums' or 'generate_pattern', leaving ambiguity about what specifically distinguishes a 'drum fill' from other drum-related generation tools.

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?

No guidance is provided on when to use this tool versus alternatives. With many sibling generation tools (e.g., generate_drums, generate_pattern, generate_bassline), the description offers no context about when a drum fill is appropriate, what scenarios it's designed for, or any prerequisites for use.

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