THIRI Chord Intelligence

analyze_chord

Read-onlyIdempotent

Parse a chord into root, quality, intervals, and (with a key) roman numeral + function. Numerals use the jazz convention by default (Cmaj7 in Am = ♭IIIΔ7); both jazz and classical numerals are always returned in numerals, and other valid readings in alternatives. Pass scale to read a minor key as harmonic or melodic minor.

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": "analyze_chord"
  }
}

Input Schema

Name	Required	Description
`key`	No
`chord`	Yes
`scale`	No	Scale to read the key in. Default: major, or natural minor with the harmonic-minor V for minor keys.
`convention`	No	Which numeral convention fills `numeral`. Default: jazz.

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 19, 2026

addedInput schema / properties / convention

Added value: +{
+  "description": "Which numeral convention fills `numeral`. Default: jazz.",
+  "enum": [
+    "jazz",
+    "classical"
+  ],
+  "type": "string"
+}

addedInput schema / properties / scale

Added value: +{
+  "description": "Scale to read the key in. Default: major, or natural minor with the harmonic-minor V for minor keys.",
+  "enum": [
+    "major",
+    "natural_minor",
+    "harmonic_minor",
+    "melodic_minor"
+  ],
+  "type": "string"
+}

First observedJun 18, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive, so the safety profile is covered. The description adds real behavioral value by disclosing that both jazz and classical numerals are always returned in `numerals`, alternate readings in `alternatives`, and that jazz is the default convention.

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 dense sentences, front-loaded with the core action and outputs. The numerals/alternatives clause is somewhat packed but every sentence carries distinct information with no filler.

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?

No output schema exists, so the description usefully names the returned fields (`numeral`, `numerals`, `alternatives`). Combined with annotation coverage, an agent has enough to invoke and interpret results, though exact return shapes beyond numerals are unstated.

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?

With only 50% schema coverage, the description compensates: it explains what `key` triggers, how `scale` reads minor keys, and that `convention` only controls which numeral fills the `numeral` field. The `chord` parameter itself is self-evident from the tool name.

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 ('Parse a chord') and enumerates the exact outputs (root, quality, intervals, roman numeral + function). This clearly separates it from siblings like generate_voicing or reharmonize, which create rather than analyze.

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?

Gives clear conditional context: numerals require a `key`, and `scale` selects harmonic/melodic minor readings. However, it never names an alternative tool or states when a different sibling (e.g. resolve_chord) would be the better pick.

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

All THIRI Chord Intelligence 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.