Skip to main content
Glama

Transpose Chords

transpose_chords
Read-onlyIdempotent

Transpose a line or chart of chord symbols by a number of semitones, keeping chord qualities and slash bass notes (C/E becomes D/F# up 2). Returns the transposed text with the original spacing and a link to the browser transposer. Works on chord symbols only: not audio, lyrics or notation files.

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": {
      "chords": "<chords>",
      "semitones": "<semitones>"
    },
    "name": "transpose_chords"
  }
}

Input Schema

NameRequiredDescriptionDefault
chordsYesChord symbols separated by spaces or line breaks, as written on a lead sheet, for example "C G/B Am F".
semitonesYesHow far to move: positive is up, negative is down. 12 is one octave; capo 2 to concert pitch is -2.
preferFlatsNoSpell accidentals as flats (Bb, Eb) instead of sharps; use for flat keys such as F, Bb or Eb.

Output Schema

NameRequiredDescriptionDefault
chordsYesThe transposed chord text.
browserToolYesLink to the matching free browser tool on clefdrills.com, to share with the user.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • addedInput schema / properties / chords / description
      Added value: +"Chord symbols separated by spaces or line breaks, as written on a lead sheet, for example \"C G/B Am F\"."
    • addedInput schema / properties / preferFlats / description
      Added value: +"Spell accidentals as flats (Bb, Eb) instead of sharps; use for flat keys such as F, Bb or Eb."
    • addedInput schema / properties / semitones / description
      Added value: +"How far to move: positive is up, negative is down. 12 is one octave; capo 2 to concert pitch is -2."
    • 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"
      +    },
      +    "chords": {
      +      "description": "The transposed chord text.",
      +      "type": "string"
      +    }
      +  },
      +  "required": [
      +    "chords",
      +    "browserTool"
      +  ],
      +  "type": "object"
      +}
  2. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), so the description is not obligated to restate it. It instead adds real behavioral detail: chord qualities and slash bass notes are preserved (C/E becomes D/F# up 2), original spacing is retained, and a browser link is returned — behavior an agent could not derive from the schema or annotations.

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

Conciseness5/5

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

Three sentences, front-loaded with the core action, followed by the output shape and then the scope limit. Every sentence carries distinct information with no restatement of the name or title.

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

Completeness5/5

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

For a small three-parameter pure-function tool with full schema coverage, complete annotations and an output schema, the description covers action, transformation semantics, output shape and scope exclusions. Nothing an agent needs in order to call it correctly is missing.

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 description coverage is 100%, with each parameter (chords, semitones, preferFlats) already documented including units and direction. The description only reinforces semitone semantics via the C/E → D/F# example and adds nothing about preferFlats or the input length limit, so baseline 3 applies.

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?

States a specific verb and resource ('Transpose a line or chart of chord symbols') plus the transformation unit (semitones). The closing sentence explicitly excludes audio, lyrics and notation files, which cleanly separates it from siblings like tab_to_piano_notes and spell_piano_chord.

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 description gives an explicit when-not boundary ('Works on chord symbols only: not audio, lyrics or notation files'), which is the most common mis-selection risk here. It does not positively name a sibling to use instead, so routing between chord tools is still partly inferential.

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