Skip to main content
Glama

Suggest songs for a set

suggest_songs

Find songs for building a setlist by filtering the repertoire by musical key and/or BPM range, including upbeat requests in a specific key.

Instructions

Suggest songs for building a set, filtered by key and/or BPM range. Useful for 'give me upbeat songs in G' style requests.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "suggest_songs"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
bpm_maxNo
bpm_minNo
song_keyNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden. It never explains what "suggest" actually means behaviorally — whether results are ranked, randomized, scored against an existing set, or personalized — nor does it cover result size, ordering, or empty-result behavior.

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?

Two short sentences with the primary purpose front-loaded and no redundant restatement of the title. The example sentence earns its place by clarifying the intended request shape.

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

Completeness2/5

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

For a no-annotation, no-output-schema tool with four undocumented parameters, the description is too thin: it leaves the ranking/selection logic, the limit behavior, and key format unresolved. An agent could call it, but could not predict or interpret the results confidently.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must compensate. It only gestures at song_key and the BPM bounds via "filtered by key and/or BPM range" and the "in G" example; the limit parameter (default 10, max 50) is never mentioned, and key formatting ("G" vs "Gm" vs "Am") remains ambiguous.

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?

Uses a specific verb ("suggest") plus the resource (songs) and the intended outcome (building a set), which distinguishes it from the plain enumerator sibling list_songs. It does not explicitly name the sibling it differs from, so it stops short of a 5.

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 example phrase "give me upbeat songs in G" implies the request pattern it serves, and "filtered by key and/or BPM range" indicates optional filters. It gives no explicit when-not guidance and never says why an agent should choose this over list_songs or get_setlist.

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