Skip to main content
Glama
slshults

gpra-chord-charts-mcp

by slshults
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Get a chord chart by id

get_chord_chart_by_id
Read-only

Fetch a chord chart by numeric ID to re-render a previously viewed voicing without searching again. Includes text diagram and PNG URL.

Instructions

Fetch one specific chord voicing by its numeric id, as returned by get_chord_chart_by_name. Use this to re-render a chart the user already saw without looking it up again.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesNumeric chord id.
formatNoWhich representations to return. Defaults to "text", which includes a direct URL to a PNG of the chart — embed that where your surface renders images. Use "image" or "both" only if you need the PNG bytes inline; they cost image tokens and many clients bury them.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • changedInput schema / properties / format / description
      Previous value: -"Which representations to return. Defaults to \"both\". Use \"text\" when the user does not want images or the client cannot display them, and \"image\" when only the diagram is wanted."New value: +"Which representations to return. Defaults to \"text\", which includes a direct URL to a PNG of the chart — embed that where your surface renders images. Use \"image\" or \"both\" only if you need the PNG bytes inline; they cost image tokens and many clients bury them."
    • removedInput schema / properties / id / exclusiveMinimum
      Removed value: -0
    • addedInput schema / properties / id / minimum
      Added value: +-9007199254740991
  2. First observedv0.1.0

TDQS

A4.2/5.0
Behavior3/5

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

The readOnlyHint annotation already covers the safety profile, so the description only needs to add selective context. It adds the id provenance and reuse intent, but discloses no additional behavioral traits such as error handling, caching, or response details.

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 sentences, with the core action and id source front-loaded and the use case following immediately. No filler or redundant restatement of the title.

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 simple read-only lookup with fully described parameters and no nested objects, the description provides enough context. The format parameter schema covers return-representation behavior, though the main description does not describe the response shape or error case.

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 adds value beyond the schema by explaining that the id comes from a prior get_chord_chart_by_name call, which tells the agent where the id originates and reinforces the re-render scenario.

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 (fetch), a specific resource (one chord chart/voicing by numeric id), and ties it to the sibling get_chord_chart_by_name. The re-render use case further clarifies its distinct role.

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?

The description clearly says to use this when re-rendering a chart the user already saw, avoiding a fresh lookup. It references get_chord_chart_by_name as the source of the id, but does not explicitly contrast with get_chord_of_the_day.

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