Skip to main content
Glama

HumMatch

by me.hummatch
OverviewDiscussionsAdmin

Search the song catalog

search_songs
Read-onlyIdempotent

Search HumMatch by song title or artist. Use this to resolve a song someone named into the catalog slug that check_song_fit needs, or to look up a song's measured vocal range. Pass rangeLow/rangeHigh as well to score every result against that voice and get the hits ranked by fit.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
qYesSearch text: a song title, an artist, or both.
limitNoMaximum results (default 20, max 50).
rangeLowNoOptional. Lowest note of the singer, to score and rank the results by fit.
rangeHighNoOptional. Highest note of the singer, to score and rank the results by fit.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
countNo
queryYes
songsYesResults. Scored fields are present only when rangeLow and rangeHigh were supplied.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedOutput schema / properties / songs / items / properties / rangeConfidence / description
      Previous value: -"How the range was established. \"verified\" was measured from the recording; \"estimated\" was derived from published sources and should be presented as guidance, not fact; \"unknown\" means no range data."New value: +"How the range was established, strongest first. \"manual_research\" was researched against sheet music or a score and is the most trustworthy tier. \"estimated\" was derived from published sources rather than measured, so present those scores as guidance rather than fact. \"high\" and \"low\" are legacy confidence labels. \"unknown\" means no range data."
    • addedOutput schema / properties / songs / items / properties / rangeConfidence / enum
      Added value: +[
+  "manual_research",
+  "estimated",
+  "high",
+  "low",
+  "unknown"
+]
  2. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "count": {
+      "type": "integer"
+    },
+    "query": {
+      "type": "string"
+    },
+    "songs": {
+      "description": "Results. Scored fields are present only when rangeLow and rangeHigh were supplied.",
+      "items": {
+        "properties": {
+          "artist": {
+            "type": "string"
+          },
+          "difficultyScore": {
+            "description": "Karaoke difficulty, 0-100. Higher is harder.",
+            "type": [
+              "integer",
+              "null"
+            ]
+          },
+          "genre": {
+            "type": "string"
+          },
+          "highNote": {
+            "description": "Highest note of the song as a MIDI number.",
+            "type": [
+              "integer",
+              "null"
+            ]
+          },
+          "highNoteName": {
+            "description": "Same as highNote, as a note name like \"C#5\".",
+            "type": "string"
+          },
+          "likelyVoiceFit": {
+            "type": "string"
+          },
+          "lowNote": {
+            "description": "Lowest note of the song as a MIDI number.",
+            "type": [
+              "integer",
+              "null"
+            ]
+          },
+          "lowNoteName": {
+            "description": "Same as lowNote, as a note name like \"G2\".",
+            "type": "string"
+          },
+          "matchScore": {
+            "description": "Overall suitability for this voice, 0-100.",
+            "type": "integer"
+          },
+          "rangeConfidence": {
+            "description": "How the range was established. \"verified\" was measured from the recording; \"estimated\" was derived from published sources and should be presented as guidance, not fact; \"unknown\" means no range data.",
+            "type": "string"
+          },
+          "rangeSource": {
+            "description": "Provenance tag for the range, e.g. \"estimated_curated_seed\".",
+            "type": "string"
+          },
+          "riskWarning": {
+            "type": "string"
+          },
+          "slug": {
+            "description": "Catalog slug; the identifier check_song_fit takes.",
+            "type": "string"
+          },
+          "suggestedKey": {
+            "description": "Transposition advice, e.g. \"Try a lower key\".",
+            "type": "string"
+          },
+          "tessituraScore": {
+            "description": "How comfortable the song sits where the voice spends most time, 0-100.",
+            "type": "integer"
+          },
+          "title": {
+            "type": "string"
+          },
+          "url": {
+            "description": "Canonical HumMatch page for the song.",
+            "type": "string"
+          },
+          "vocalFitScore": {
+            "description": "How well the song range sits inside the singer range, 0-100.",
+            "type": "integer"
+          },
+          "voiceTypeFitScore": {
+            "description": "Fit against the voice type lane, 0-100. Can be high while matchScore is low when the range still exceeds the singer.",
+            "type": "integer"
+          },
+          "whyItFits": {
+            "type": "string"
+          },
+          "year": {
+            "type": [
+              "integer",
+              "null"
+            ]
+          }
+        },
+        "required": [
+          "slug",
+          "title",
+          "artist",
+          "rangeConfidence"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "required": [
+    "query",
+    "songs"
+  ],
+  "type": "object"
+}
  3. First observed

TDQS

A4.7/5.0
Behavior4/5

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

Beyond readOnlyHint annotations, the description discloses that providing rangeLow/rangeHigh scores every result and ranks by fit, and that it resolves songs to catalog slugs. This adds behavioral context not captured in annotations, though it could mention behavior when no results are found.

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 sentences, each serving a purpose: purpose, use cases, and parameter behavior. No filler or redundancy.

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?

Output schema exists, so return format is covered. The description explains use cases, relation to check_song_fit, ranking behavior, and parameter usage, making it complete for this tool.

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 fully describes all 4 parameters, and the description adds semantic context: q searches title or artist, rangeLow/rangeHigh are used for scoring/ranking results. Limit is self-explanatory, so the description provides meaningful value beyond the schema.

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 opens with 'Search HumMatch by song title or artist' – a specific verb and resource. It further distinguishes from siblings by noting check_song_fit needs the catalog slug from this tool and that it can look up a song's measured vocal range.

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?

'Use this to resolve a song someone named into the catalog slug that check_song_fit needs' explicitly gives when-to-use context, and the rangeLow/rangeHigh guidance explains when to enrich the search. This clearly positions the tool relative to alternatives.

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

All HumMatch toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources