ScorpTech x402 Tools

Music Interval

music_interval

Read-onlyIdempotent

The interval between two written notes. The number comes from the letters and the quality from the semitones, so C to E is a major third and C to Fb is a diminished fourth. Direction follows the written notes. Semitones is negative when the second note is lower. Price: $0.001 USDC per successful call (x402, Solana). Same tool over HTTPS: GET https://scorptech.it.com/api/x402/v1/music-interval

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": {
      "from": "<from>",
      "to": "<to>"
    },
    "name": "music_interval"
  }
}

Input Schema

Name	Required	Description	Default
`to`	Yes
`from`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 23, 2026

TDQS

A3.5/5.0

Behavior4/5

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

Annotations already cover safety (readOnly, idempotent, non-destructive), and the description adds genuinely new context: the price ($0.001 USDC per successful call, x402/Solana), an alternate HTTPS endpoint, and the sign convention for direction. It does not describe failure behavior for unparseable notes, which is the remaining gap.

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?

Definition and examples come first, followed by directional semantics, then billing/transport. Every sentence carries information; the pricing/URL trailer is boilerplate but practically necessary for a paid x402 tool.

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?

With no output schema, the description steps in to explain the result: the number comes from the letters, the quality from the semitones, and a negative semitone count signals a descending interval. Missing only the accepted input syntax for note strings.

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 coverage is 0%, so the burden falls largely on the description. It never names 'from' and 'to' or states the accepted note format (e.g. 'C4' vs 'C#'), though 'Direction follows the written notes' and 'semitones is negative when the second note is lower' imply the first param is the lower/first note. Partial compensation only.

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?

Names a specific musical quantity and defines it precisely: 'The interval between two written notes,' with examples (C to E = major third, C to Fb = diminished fourth). It does not name or contrast with the related siblings music_chord, music_scale, or music_transpose, so the boundary is left implicit.

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?

There is no statement of when to use this instead of music_transpose, music_scale, or midi_note, and no prerequisites or exclusion conditions. The examples illustrate the computation but do not route the agent between alternatives.

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?