Skip to main content
Glama

music_scales

Browse and filter scales, or inspect a root and scale for note spellings, degrees, modes, seventh chords, and Live 12 scale names to guide composition and song-scale setup.

Instructions

Scales and modes knowledge. Without arguments, lists all ~50 scales (church modes, harmonic/melodic minor families, pentatonics, blues, bebop, symmetric, Japanese, gamelan, flamenco...) with their character and typical styles; query filters (e.g. "flamenco", "jazz", "sombre"). With root and scale, details one scale: notes spelled in the key, degrees, characteristic note, character, styles, diatonic seventh chords with roman numerals and functions, the other modes with the same notes, and Live 12's scale name (for set_song_scale).

Parameters:

  • query: Text to filter the list

  • root: Tonic (e.g. "D", "Eb") to detail one scale

  • scale: Scale name (e.g. "dorian", "phrygian dominant", "hijaz", "harmonic minor")

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "music_scales"
  }
}

Input Schema

NameRequiredDescriptionDefault
rootNo
queryNo
scaleNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.1.1

TDQS

A4.4/5.0
Behavior4/5

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

With no annotations, the description carries the full burden, and it does disclose substantial behavior: the size of the list (~50), the categories covered, what filtering matches on ('flamenco', 'jazz', 'sombre'), and the detailed payload including spelled notes, degrees, seventh chords, modes with the same notes, and Live 12 naming. It does not state what happens with `root` alone or an unrecognized scale name, nor explicitly that the tool is read-only — the only real gaps for a knowledge tool.

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?

Front-loaded with purpose, then call modes, then a compact parameter list with examples — easy to scan. The trailing parameter block partially restates what the prose already established about query/root/scale, which is mild redundancy but aids quick lookup.

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?

An output schema exists, yet the description still previews the detailed payload (chords, roman numerals, functions, Live 12 scale name), which is useful for deciding whether one call suffices. For a 3-optional-parameter knowledge tool this is nearly complete; only edge-case behavior for partial arguments is unaddressed.

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

Parameters5/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: all three parameters are defined with concrete example values ('D', 'Eb' / 'dorian', 'phrygian dominant', 'hijaz'), the filter target is illustrated with both styles and mood terms, and the root+scale combination is described as jointly triggering detail mode.

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 uses a specific verb+resource framing ('Scales and modes knowledge') and then spells out two distinct behaviors: listing ~50 scales with character and styles, or detailing one scale from root+scale. It also names the downstream consumer (set_song_scale) so the agent can separate this knowledge lookup from sibling tools like music_styles or music_chord_ideas.

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?

It gives explicit call patterns: no arguments to list, `query` to filter, `root`+`scale` to detail. That is clear when-to-use guidance for each mode. It stops short of stating exclusions (e.g., that this is not the tool that actually changes the song scale), leaving the boundary established only implicitly by referencing set_song_scale.

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