Skip to main content
Glama

Get a song

get_song

Retrieve a single song by its ID, including its chord chart and rehearsal notes, to review performance details.

Instructions

Get one song by id, including its chord chart and rehearsal notes.

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": {
      "song_id": "<song_id>"
    },
    "name": "get_song"
  }
}

Input Schema

NameRequiredDescriptionDefault
song_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.3/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden. It discloses the payload contents, which is genuinely useful, but says nothing about not-found/error behavior for a bad id, permissions, or whether the chord chart and notes are always present or may be empty.

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?

One short sentence, front-loaded with the action and scope, with the return contents appended. Nothing is wasted or buried.

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 a simple one-parameter getter with no output schema, the description does the minimum-plus by naming returned fields. It falls short on error semantics and on whether other song fields are also returned, which matters because there is no output schema to consult.

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 single parameter has 0% schema description coverage, but the schema itself names it song_id and types it as a uuid, so the description's 'by id' adds only confirmation. It does not clarify format expectations or what a non-existent id produces.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/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 ('Get one song by id') and adds what the payload contains (chord chart, rehearsal notes). It clearly contrasts with a bulk listing in spirit, though it never names list_songs as the alternative.

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?

'By id' implies the caller must already hold a song identifier, which is the only usage signal given. There is no explicit when-to-use versus list_songs/get_setlist guidance and no statement of when this tool is the wrong choice.

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