Skip to main content
Glama

Zovo Chord Chart Maker

Generate chord chart

generate_chord_chart
Read-onlyIdempotent

Use this when the user wants a guitar chord chart printable, a ukulele chord chart, a piano chord chart, or chord diagrams for a song. Convert a pasted song or an uploaded photo of a chord sheet into the chords list (chord names like G, Em, F#m7, C/E); use chord_sheet only to pass raw pasted text. Draws one diagram per different chord as a print-ready PDF (US Letter or A4, 6, 12 or 24 per page) for guitar in standard tuning, ukulele (G C E A) or piano, with optional transpose, capo (or "auto"), and left-handed diagrams. Guitar and ukulele shapes are checked by their notes. Does not do alternate tunings, bass, tabs or notation.

Input Schema

NameRequiredDescriptionDefault
capoNoGuitar or ukulele capo fret 0-9, or "auto" to pick the capo with the easiest open shapes. Default 0. A "Capo 2" line in chord_sheet is read too.
paperNoletter (US Letter, default) or a4.
titleNoHeading printed on the sheet, e.g. the song name "Wonderwall" or "Beginner chords". Default "Chord chart".
chordsNoChord names, one per item, e.g. ["G", "Em", "C", "D7", "F#m7b5", "C/E"]. Convert a pasted song or a photo of a chord sheet into this list of the chords it uses. Repeats are drawn once. Up to 64 different chords.
to_keyNoTranspose to this key instead of giving semitones, e.g. G or Bbm. The original key is from_key, a Key: line in the sheet, or the first chord.
from_keyNoThe song's current key when to_key is used, e.g. E. Optional.
per_pageNoDiagrams per page: 6, 12 (default) or 24.
capo_modeNoHow chord names relate to the capo: "shapes" (default with a capo number) means the names are the shapes you finger, as chord sheets that say "Capo 2" write them; each diagram says which chord sounds. "sounding" means the names are the chords that should sound, and the tool finds the shapes to play with the capo (used for capo "auto").
instrumentNoguitar (standard tuning E A D G B E, default), ukulele (G C E A) or piano (keyboard diagrams). Several, e.g. "guitar and ukulele", give one PDF with each instrument on its own pages.
chord_sheetNoFallback: a pasted chord sheet (chords over lyrics, or inline [Am] chords). Every chord in it is drawn once, in order of first use. Example: "G Em\nHello my friend\nC D\nHow are you".
left_handedNotrue for mirrored left-handed diagrams (low string on the right). Default false.
shapes_per_chordNoHow many positions to draw per chord, 1 (default) to 4, lowest on the neck first.
show_finger_numbersNoPrint finger numbers in the dots (default true).
transpose_semitonesNoShift every chord up (positive) or down (negative) by this many semitones before drawing, e.g. 2 or -3. Default 0.

Output Schema

NameRequiredDescriptionDefault
capoYes
notesYes
pagesYes
paperYes
titleYes
tuningYes
skippedYes
diagramsYes
per_pageYes
downloadsYes
instrumentYes
chord_countYes
left_handedYes
diagram_countYes
diagrams_shownNo
transpose_semitonesYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already declare this as a safe, idempotent, closed-world read, so the burden is low; the description still adds real behavior: output is a print-ready PDF, one diagram per distinct chord, repeats collapse, a 64-distinct-chord ceiling, and chord shapes are validated by their notes.

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 the use case, followed by input guidance and then capability limits, so an agent can stop reading early and still call correctly. The middle sentence is long and clause-heavy, packing paper sizes, per-page counts, instruments and transpose/capo options into one run-on, which costs a point.

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?

Complete for a 14-parameter generator: it covers supported instruments and tunings, output format and page sizes, transposition/capo semantics, input conversion paths, and enumerated exclusions. Return values need no explanation because an output schema exists.

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 coverage is 100%, so the baseline is 3; the description earns extra credit by clarifying the division of labor between 'chords' (converted song/photo) and 'chord_sheet' (raw pasted text only) and by calling out capo 'auto' and the standard-tuning/uke limitations that the schema alone does not convey.

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 (generate/draw) and resource (printable chord chart PDF) plus the instruments and card layouts it covers. An agent can easily separate this from find_chord_fingerings, which looks up individual shapes rather than rendering a chart document.

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?

Opens with an explicit trigger sentence ('Use this when the user wants a ... printed chord chart') and closes with clear exclusions ('Does not do alternate tunings, bass, tabs or notation'). It also routes input handling ('use chord_sheet only to pass raw pasted text') but never names the sibling find_chord_fingerings as the alternative for single-chord lookups.

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