Skip to main content
Glama
williamzujkowski

Strudel MCP Server

generate_scale

Generate musical scale notes by specifying a root note and scale type for music creation and pattern development.

Instructions

Generate scale notes

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
rootYesRoot note
scaleYesScale type

Implementation Reference

  • Handler executes the generate_scale tool: validates root note and scale name, calls MusicTheory.generateScale, formats and returns the scale notes.
    case 'generate_scale':
      InputValidator.validateRootNote(args.root);
      InputValidator.validateScaleName(args.scale);
      const scaleNotes = this.theory.generateScale(args.root, args.scale);
      return `${args.root} ${args.scale} scale: ${scaleNotes.join(', ')}`;
  • Tool registration in getTools(): defines name, description, and input schema for generate_scale.
    {
      name: 'generate_scale',
      description: 'Generate scale notes',
      inputSchema: {
        type: 'object',
        properties: {
          root: { type: 'string', description: 'Root note' },
          scale: { type: 'string', description: 'Scale type' }
        },
        required: ['root', 'scale']
      }
    },
  • Core helper function in MusicTheory class: generates scale notes from root and scale intervals using modulo 12 transposition.
    generateScale(root: string, scaleName: keyof typeof this.scales): string[] {
      const noteNames = ['C', 'C#', 'D', 'D#', 'E', 'F', 'F#', 'G', 'G#', 'A', 'A#', 'B'];
      const rootIndex = noteNames.indexOf(root.toUpperCase());
      if (rootIndex === -1) {
        throw new Error(`Invalid root note: ${root}`);
      }
      
      const scale = this.scales[scaleName];
      if (!scale) {
        throw new Error(`Invalid scale: ${scaleName}`);
      }
      
      return scale.map(interval => {
        const noteIndex = (rootIndex + interval) % 12;
        return noteNames[noteIndex];
      });
    }
Behavior1/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure but fails completely. It doesn't indicate whether this is a read or write operation, what the output format might be, whether it has side effects, or any behavioral characteristics. For a tool that presumably generates musical content, this lack of transparency is particularly problematic.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

While the description is extremely concise (only two words), this represents under-specification rather than effective conciseness. The description doesn't earn its place by providing meaningful information. A truly concise description would still convey essential purpose and context, which this one fails to do.

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 the complexity of a musical generation tool with no annotations and no output schema, the description is completely inadequate. It doesn't explain what the tool returns, how the output is structured, or any behavioral characteristics. For a tool that presumably creates musical scale data, this minimal description leaves critical 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 schema description coverage is 100%, with both parameters ('root' and 'scale') having descriptions in the schema. The tool description adds no additional parameter information beyond what's already in the structured schema. According to the scoring guidelines, when schema coverage is high (>80%), the baseline score is 3 even with no parameter information in the description.

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 'Generate scale notes' is a tautology that essentially restates the tool name 'generate_scale'. It lacks specificity about what resource is being generated (musical scale notes) and doesn't distinguish this tool from sibling tools like 'apply_scale' or 'detect_key'. The description fails to provide a clear verb+resource combination that would help an agent understand the tool's function.

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?

The description provides absolutely no guidance about when to use this tool versus alternatives. There's no mention of context, prerequisites, or comparison to sibling tools like 'apply_scale' or 'detect_key'. An agent would have no basis for choosing this tool over other musical scale-related tools in the server.

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