Skip to main content
Glama

Find Music Guides

find_music_guides
Read-onlyIdempotent

Search Clef guides about converting, reading and learning music (MIDI, PDF scores, guitar tab, chord charts, piano apps). Use it when the user asks how to do a music workflow rather than for a computed answer. Returns up to 8 guides with title, description and resource uri (read the uri for the full guide) plus a link to the guide directory. Guides explain workflows; they do not convert files.

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": {
      "query": "<query>"
    },
    "name": "find_music_guides"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYesPlain words describing the task, for example "midi to sheet music" or "learn pop songs on piano". Matched against guide titles and descriptions.

Output Schema

NameRequiredDescriptionDefault
guidesYesBest matches first; empty when nothing matched.
directoryYesPage listing every Clef music conversion guide.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / query / description
      Added value: +"Plain words describing the task, for example \"midi to sheet music\" or \"learn pop songs on piano\". Matched against guide titles and descriptions."
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "$schema": "http://json-schema.org/draft-07/schema#",
      +  "additionalProperties": false,
      +  "properties": {
      +    "directory": {
      +      "description": "Page listing every Clef music conversion guide.",
      +      "type": "string"
      +    },
      +    "guides": {
      +      "description": "Best matches first; empty when nothing matched.",
      +      "items": {
      +        "additionalProperties": false,
      +        "properties": {
      +          "description": {
      +            "type": "string"
      +          },
      +          "title": {
      +            "type": "string"
      +          },
      +          "uri": {
      +            "description": "Guide URL; also readable with resources/read.",
      +            "type": "string"
      +          }
      +        },
      +        "required": [
      +          "title",
      +          "description",
      +          "uri"
      +        ],
      +        "type": "object"
      +      },
      +      "type": "array"
      +    }
      +  },
      +  "required": [
      +    "guides",
      +    "directory"
      +  ],
      +  "type": "object"
      +}
  2. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint=false and destructiveHint=false, so the safety profile is covered. The description still adds real context beyond them: a result cap of 8 guides, the per-result fields (title, description, resource uri), an instruction to read the uri for the full guide, and a directory link. The only minor gap is that it does not say what an empty result looks like.

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?

Three short sentences, front-loaded with the search purpose, then routing condition, then return shape. The closing 'they do not convert files' is a deliberate boundary reinforcement rather than filler, so nothing should be cut.

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?

For a one-parameter, read-only search tool with an output schema and full annotation coverage, this covers purpose, routing, result shape and the follow-up action (read the uri). An agent has everything needed to call it and to act on the response.

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?

Schema coverage is 100% and the single 'query' parameter is fully documented in the schema, including length bounds and example phrasings. The description's phrase 'guides about converting, reading and learning music' loosely frames good query terms but adds no syntax, format or matching detail beyond what the schema states.

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 and resource ('Search Clef guides about converting, reading and learning music') and enumerates the covered domains (MIDI, PDF scores, guitar tab, chord charts, piano apps). It also separates itself from the sibling computation tools by saying it is for 'how to do a music workflow rather than for a computed answer'.

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

Usage Guidelines5/5

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

Gives an explicit when-to-use condition (user asks how to do a music workflow) and an explicit when-not (a computed answer), which is exactly the axis that distinguishes it from spell_piano_chord, tab_to_piano_notes and transpose_chords. No inference is required to route to this tool.

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