Skip to main content
Glama
williamzujkowski

Strudel MCP Server

by williamzujkowski
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Local

apply_scale

Generate musical scales by specifying a root note and scale name for use in Strudel.cc pattern creation and music generation.

Instructions

Apply scale to notes

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
scaleYesScale name
rootYesRoot note

Implementation Reference

  • src/server/EnhancedMCPServerFixed.ts:350-361 (registration)
    Registration of the 'apply_scale' tool, including its input schema definition. No separate handler implementation found; tool execution would fall to default error in executeTool.
    {
  name: 'apply_scale',
  description: 'Apply scale to notes',
  inputSchema: {
    type: 'object',
    properties: {
      scale: { type: 'string', description: 'Scale name' },
      root: { type: 'string', description: 'Root note' }
    },
    required: ['scale', 'root']
  }
},

Tool Definition Quality

D1.7/5.0
Behavior1/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. However, it offers no information about what 'apply scale' does behaviorally—whether it modifies existing notes, creates new ones, requires specific permissions, has side effects, or what the expected outcome is. This is inadequate for a tool with no annotation coverage.

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 concise with only three words, it is under-specified rather than efficiently informative. It lacks front-loaded critical details and fails to convey essential operational meaning, making it ineffective despite its brevity. Conciseness should not come at the cost of clarity.

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 implied by the tool name (potentially involving musical or data transformation), lack of annotations, no output schema, and a vague description, this is highly incomplete. The description does not explain what the tool does, how to use it, what it returns, or how it fits with siblings, leaving significant gaps for an agent to understand and invoke it correctly.

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 clear documentation for both parameters ('scale' and 'root'). The description adds no additional semantic context beyond what the schema provides, such as examples of scale names or root note formats. Since schema coverage is high, the baseline score of 3 is appropriate, as the description does not compensate but also does not detract.

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 'Apply scale to notes' is a tautology that essentially restates the tool name 'apply_scale' without adding meaningful specificity. It mentions the action ('apply') and target ('notes') but provides no details about what 'apply' means operationally, what 'notes' refers to (e.g., musical notes, text notes, data notes), or how this differs from sibling tools like 'generate_scale' or 'transpose'.

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 no guidance on when to use this tool versus alternatives. It does not mention any context, prerequisites, or exclusions, nor does it reference sibling tools like 'generate_scale' or 'transpose' that might serve similar or related functions. This leaves the agent with no information to make an informed choice among available options.

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