Skip to main content
Glama

Spell Piano Chord

spell_piano_chord
Read-onlyIdempotent

List the notes of one chord symbol as piano pitches, lowest first, built up from the root in the chosen octave (a slash bass goes below). Returns each note with its name, octave and MIDI number, plus a link to the browser chord finder. Gives pitches only, not voicings over time or rhythm.

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": {
      "symbol": "<symbol>"
    },
    "name": "spell_piano_chord"
  }
}

Input Schema

NameRequiredDescriptionDefault
octaveNoOctave of the root note in scientific pitch notation; 4 puts a C root on middle C.
symbolYesOne chord symbol such as "C", "F#m7", "Bbmaj7", "Gsus4" or "D/F#". Returns an error for symbols it cannot read.

Output Schema

NameRequiredDescriptionDefault
notesYesChord tones from lowest to highest.
browserToolYesLink to the matching free browser tool on clefdrills.com, to share with the user.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • addedInput schema / properties / octave / description
      Added value: +"Octave of the root note in scientific pitch notation; 4 puts a C root on middle C."
    • addedInput schema / properties / symbol / description
      Added value: +"One chord symbol such as \"C\", \"F#m7\", \"Bbmaj7\", \"Gsus4\" or \"D/F#\". Returns an error for symbols it cannot read."
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "$schema": "http://json-schema.org/draft-07/schema#",
      +  "additionalProperties": false,
      +  "properties": {
      +    "browserTool": {
      +      "description": "Link to the matching free browser tool on clefdrills.com, to share with the user.",
      +      "type": "string"
      +    },
      +    "notes": {
      +      "description": "Chord tones from lowest to highest.",
      +      "items": {
      +        "additionalProperties": true,
      +        "properties": {
      +          "accidental": {
      +            "description": "\"#\", \"b\" or empty for a natural.",
      +            "type": "string"
      +          },
      +          "letter": {
      +            "description": "Note letter A to G.",
      +            "type": "string"
      +          },
      +          "midi": {
      +            "description": "MIDI note number, 60 = middle C.",
      +            "type": "integer"
      +          },
      +          "name": {
      +            "description": "Scientific pitch name, for example \"C4\" or \"F#3\".",
      +            "type": "string"
      +          },
      +          "octave": {
      +            "description": "Octave number in scientific pitch notation.",
      +            "type": "integer"
      +          }
      +        },
      +        "required": [
      +          "midi",
      +          "name",
      +          "letter",
      +          "accidental",
      +          "octave"
      +        ],
      +        "type": "object"
      +      },
      +      "type": "array"
      +    }
      +  },
      +  "required": [
      +    "notes",
      +    "browserTool"
      +  ],
      +  "type": "object"
      +}
  2. First observed

TDQS

A4.1/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint=false and destructiveHint=false, so safety is covered. The description still adds useful behavior: pitches are emitted lowest-first, a slash bass sits below the root, and each note carries name, octave and MIDI number. It says nothing about error handling for unparseable symbols or the cost of the external link, both of which sit outside the annotations.

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?

Three sentences, all load-bearing: purpose and construction first, return shape second, scope limit last. No filler or restated title, though the ordering rule and the slash-bass clause could be tightened into one sentence.

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?

For a two-parameter read-only tool with an output schema and full annotation coverage, the definition covers input meaning, build order and output contents adequately. Only the failure mode for unreadable symbols is left implicit, which the schema does partially carry.

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 coverage is 100%, so a baseline of 3 applies, but the description earns more by clarifying that the octave parameter positions the root and that a slash bass is placed below it, which is not spelled out in the schema. It also reinforces that symbol takes exactly one chord symbol, matching the schema's maxLength and error note.

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?

A specific verb and resource: "List the notes of one chord symbol as piano pitches." It pins down the ordering rule (lowest first), how the chord is constructed (up from the root in the chosen octave), and what a slash bass does, so an agent can distinguish it from a tab-to-notes or transpose tool without opening a schema.

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

Usage Guidelines4/5

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

The closing sentence "Gives pitches only, not voicings over time or rhythm" sets a clear negative scope that steers an agent away from expecting sequence or rhythm output. It stops short of naming an alternative tool or stating prerequisites, so it is clear context without explicit routing.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources