Skip to main content
Glama
Sign In

WritersLogic verifiable AI agents

by com.writerslogic.agents
OverviewDiscussionsAdmin

chord-check

Chord check: identify, spell, key membership, transpose — Names a chord from its notes, spells a chord symbol into notes, tests whether a chord is diatonic to a key, or transposes a chord symbol, using pitch-class arithmetic over a fixed table of 21 chord qualities, for agents handling lead sheets and music metadata. Rule-based and labelled: when several readings are equally valid (C E G A is C6 or Am7/C) or no quality in the table matches, it returns un

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

Input Schema

NameRequiredDescriptionDefault
keyNoFor key-membership.
chordNoChord symbol, root A-G with optional #/b, quality suffix, optional /bass: Cmaj7, F#m7b5, Bb/D.
notesNoFor identify: 2 to 8 notes.
preferNoAccidentals for a natural root when transposing. Default sharps; a root written with # or b keeps its kind.
operationYes
semitonesNoFor transpose: semitones up (negative down).
expectChordNoOptional claimed chord symbol to verify (identify, transpose).
expectNotesNoOptional claimed notes in order, to verify (spell).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/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 does well: it discloses the deterministic rule-based approach, the fixed 21-quality table, and the ambiguity policy (C E G A reported as C6 or Am7/C rather than silently picking one). The final clause about unmatched qualities is truncated ('it returns un'), which leaves the failure/return behavior incomplete.

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?

The definition is front-loaded with the tool name and the four operations before the mechanism and audience, which is good structure. It is dense but not padded; the only flaw is the truncated final clause, which cuts off mid-word and wastes the sentence it starts.

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

Completeness3/5

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

For an 8-parameter tool with a nested key object and no output schema, the description should explain what comes back for each operation. It gestures at return behavior via the ambiguity example but the sentence is truncated, so an agent cannot fully predict the response shape for identify, spell, or transpose.

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 coverage is 88%, so the schema already documents nearly every parameter including enums and the key sub-object. The description adds only the operation-to-parameter mapping, which is useful but largely inferable from the schema's own descriptions; baseline 3 is appropriate.

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 names a specific resource (chords) and enumerates all four operations with concrete verbs: identify from notes, spell a symbol into notes, test key membership, transpose. It also states the underlying mechanism (pitch-class arithmetic over a fixed 21-quality table), so an agent knows exactly what class of tool this is and can distinguish it from the other *-check siblings.

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?

Each operation is tied to its input mode (notes for identify, symbol for spell, key for membership, semitones for transpose), and the audience is scoped to 'agents handling lead sheets and music metadata'. There is no explicit when-not guidance or named alternative, but the operation mapping gives clear selection context.

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

All WritersLogic verifiable AI agents toolsInspect
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.

Resources