Skip to main content
Glama

music_chord_ideas

Generate reharmonisation ideas for a chord — tritone substitution, ii-V preparation, relative and borrowed chords, extensions — each with reasoning and its note spellings for quick voicing.

Instructions

Reharmonisation ideas for a chord (tritone substitution, ii-V preparation, relative chords, extensions, borrowed chords in the key), with the reason for each, plus the chord's notes.

Parameters:

  • chord: Chord symbol, e.g. "G7", "Fmaj7", "Am", "Bø", "Ebmaj7/G"

  • key_root: Key tonic, to suggest borrowed chords (optional)

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": {
      "chord": "<chord>"
    },
    "name": "music_chord_ideas"
  }
}

Input Schema

NameRequiredDescriptionDefault
chordYes
key_rootNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.1.1

TDQS

A3.7/5.0
Behavior3/5

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

With no annotations, the description must carry the behavioral burden, and it does disclose the output shape ('with the reason for each, plus the chord's notes'), which tells the agent this is a read-only advisory call. It does not state behavior for invalid or ambiguous chord symbols, nor whether results are deterministic, leaving real gaps for a no-annotation tool.

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?

Two tight blocks: purpose and output contents up front, then parameters. Every phrase earns its place, and the technique list is doing real disambiguation work rather than padding.

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, single-purpose tool with an output schema already covering return values, the description supplies what an agent needs: what it returns, what chord syntax looks like, and what key_root does. The only shortfall is unaddressed failure behavior for malformed chord symbols.

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 compensate, and it does: chord is illustrated with five concrete symbols including a slash chord and half-diminished ('Bø'), which materially constrains expected input format. key_root is explained as the key tonic and tied to its purpose (borrowed chords) and marked optional, though its own expected format is only implied.

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?

The description opens with a specific verb+resource ('Reharmonisation ideas for a chord') and enumerates the exact techniques returned (tritone substitution, ii-V preparation, relative chords, extensions, borrowed chords), which makes it obviously distinct from siblings like music_scales or music_styles. It stops short of naming or explicitly routing against any alternative, so it lands at a strong 4 rather than a 5.

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 only implied: the parenthetical on key_root ('to suggest borrowed chords') hints at when that parameter is worth supplying, and the enumeration of techniques implies when to reach for this tool. There is no explicit when-to-use/when-not-to-use statement or comparison to a sibling.

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

Deploy Server

Other Tools