Filopastry

by youwenshao

Overview Schema Source Related Servers Discussions Admin

TypeScript

Local

generate_scale

Generate musical scale notes by specifying a root note and scale type for music composition and theory applications.

Instructions

Generate scale notes

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "root": "<root>",
      "scale": "<scale>"
    },
    "name": "generate_scale"
  }
}

Input Schema

Name	Required	Description	Default
`root`	Yes	Root note
`scale`	Yes	Scale type

Schema Changelog

Changes observed during successful MCP inspections.

First observedv2.2.0Jan 26, 2026

TDQS

C2.7/5.0

Behavior1/5

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

No annotations exist, and the description provides no behavioral disclosure (e.g., side effects, return format, required permissions). For a generation tool, significant gaps exist.

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

Conciseness4/5

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

Extremely concise at three words, no wasted text. However, possibly too minimal for adequate guidance.

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?

Lacks output schema and does not explain what 'scale notes' means or what the tool returns. For a simple tool, more context about the output format 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 covers 100% of parameters with descriptions. The tool description adds no additional meaning beyond the schema, so baseline of 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

Description clearly states it generates scale notes with the tool name reinforcing this. Distinguishes itself from sibling tools like generate_melody or generate_bassline, though it lacks specificity on what exactly is generated.

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 on when to use this tool compared to alternatives like generate_pattern or suggest_pattern_from_audio. No prerequisites or context provided.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.