ScorpTech x402 Tools

Music Scale

music_scale

Read-onlyIdempotent

Spell a scale on letters from a tonic. Major, minor, harmonic minor, melodic minor (the ascending form), the church modes, pentatonic, minor pentatonic, and blues. G# major is written with E# and F##, not with flats. signature lists the accidentals in scale order. The octave does not repeat the tonic. Price: $0.001 USDC per successful call (x402, Solana). Same tool over HTTPS: GET https://scorptech.it.com/api/x402/v1/music-scale

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": {
      "note": "<note>",
      "mode": "<mode>"
    },
    "name": "music_scale"
  }
}

Input Schema

Name	Required	Description	Default
`mode`	Yes
`note`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 23, 2026

TDQS

A4.3/5.0

Behavior5/5

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

Annotations already mark the tool as read-only, idempotent, open-world, and non-destructive. The description adds substantial behavioral detail beyond annotations: enharmonic spelling rules ('G# major is written with E# and F##'), signature ordering, octave behavior, and payment/auth details via x402 on Solana.

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?

The description is front-loaded with the core purpose and mode scope, followed by useful spelling/output notes and payment details. It is generally efficient, though listing the modes partly repeats the enum and makes the description longer than strictly necessary.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

There is no output schema, so the description usefully explains that the result includes spelled letters, a signature, and no repeated tonic octave. It also covers pricing and the HTTPS alternative. Minor gaps remain around exact note syntax and full return structure, but the definition is largely complete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must carry parameter meaning. It identifies the note as the tonic, gives an input example ('G# major'), and lists the supported modes with one semantic clarification for melodic minor. It stops short of fully specifying accepted note syntax or validation rules.

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

Purpose5/5

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

The description states a specific action and resource: 'Spell a scale on letters from a tonic.' It also enumerates the supported scale families, making the scope clear and distinguishable from sibling music tools such as music_chord, music_interval, and music_transpose.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is implied by the purpose: an agent can infer this tool is for spelling scales rather than chords or intervals. However, the description does not explicitly state when to choose it over the sibling music tools or mention exclusions, so guidance remains implicit.

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

All ScorpTech x402 Tools tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?