Skip to main content
Glama
williamzujkowski

Strudel MCP Server

add_swing

Apply swing to music patterns by adjusting rhythmic timing with a specified amount parameter to create syncopated grooves.

Instructions

Add swing to pattern

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
amountYesSwing amount (0-1)

Implementation Reference

  • Executes the add_swing tool by appending `.swing(${args.amount})` to the current pattern and writing it back.
    case 'add_swing':
      InputValidator.validateNormalizedValue(args.amount, 'amount');
      const currentSwing = await this.getCurrentPatternSafe();
      const withSwing = currentSwing + `.swing(${args.amount})`;
      await this.writePatternSafe(withSwing);
      return `Added swing: ${args.amount}`;
  • Defines the tool schema including name, description, and input schema requiring 'amount' as a number between 0-1.
      name: 'add_swing',
      description: 'Add swing to pattern',
      inputSchema: {
        type: 'object',
        properties: {
          amount: { type: 'number', description: 'Swing amount (0-1)' }
        },
        required: ['amount']
      }
    },
  • Registers the list tools handler which returns all tools including add_swing via getTools().
    this.server.setRequestHandler(ListToolsRequestSchema, async () => ({
      tools: this.getTools()
    }));
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 swing' implies a mutation operation, but the description doesn't specify whether this modifies an existing pattern in-place, creates a new pattern, requires specific permissions, has side effects, or what the expected outcome is. It lacks critical details about behavior beyond the basic action.

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 with just three words, front-loading the core action. There's no wasted language or unnecessary elaboration, making it efficient for quick scanning while still conveying the basic purpose.

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 complexity of a musical timing modification tool with no annotations and no output schema, the description is incomplete. It doesn't explain what swing does musically, how it affects the pattern, what the return value or result looks like, or error conditions. For a tool that likely modifies musical data, this leaves significant gaps in understanding.

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 the 'amount' parameter clearly documented as 'Swing amount (0-1)'. The description adds no additional parameter semantics beyond what the schema provides, but since schema coverage is high, the baseline score of 3 is appropriate as the schema adequately handles parameter documentation.

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 swing to pattern' states a basic action but is vague about what 'swing' means in this musical context and what 'pattern' refers to. It doesn't distinguish this tool from sibling tools like 'humanize' or 'quantize' that might also modify timing. The description restates the tool name without adding specificity.

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. With sibling tools like 'humanize', 'quantize', and 'generate_euclidean' that might affect timing or rhythm, the description offers no context about when swing is appropriate, what musical styles it applies to, or prerequisites like needing an existing pattern loaded.

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