Skip to main content
Glama
slshults

gpra-chord-charts-mcp

by slshults
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Chord of the day

get_chord_of_the_day
Read-only

Retrieve today's chord chart from Guitar Practice Routine App as text or PNG, providing a daily practice prompt for learning chords.

Instructions

Return today's Chord of the Day from Guitar Practice Routine App — the same chord posted to the app's Bluesky and Facebook feeds that day. Useful as a practice prompt or a daily nudge for someone learning chords.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
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. Changed1 schema field 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."
  2. First observedv0.1.0

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint and openWorldHint, so the safety and openness profile is covered. The description adds provenance (same chord as the social feeds) but no further behavioral details such as caching, availability, or edge cases; given the annotations, a 3 is appropriate.

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 sentences with no filler: the first states the core action and source, the second adds a legitimate use case. The description is front-loaded and every sentence earns its place.

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 tool with one optional parameter, the description explains the daily nature, the source, and the practical purpose, while the schema covers format options. It could explicitly describe the returned representation, but nothing essential is missing.

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?

The tool description itself does not explain the format parameter, but the input schema provides 100% coverage with a detailed description of the default, use cases, and token-cost warning. Since the schema carries the parameter meaning, the baseline score of 3 applies.

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 states a specific verb and resource: return today's Chord of the Day from the Guitar Practice Routine App, and clarifies it matches the chord posted to the app's social feeds that day. This makes it clearly distinguishable from siblings that fetch by id or name.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description gives a practical use case—practice prompt or daily nudge—but does not explicitly state when to prefer this tool over get_chord_chart_by_id or get_chord_chart_by_name. Usage guidance is implied rather than made explicit with exclusions or alternatives.

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