HumMatch

Build a vocal profile

get_vocal_profile

Read-onlyIdempotent

Turn a singer's vocal range into a normalized HumMatch vocal profile: a persistent Vocal ID, voice type, and tone label. Call this first when you know someone's range and want a profile to reuse across the other HumMatch tools.

Input Schema

TableJSON Schema

Name	Required	Description
`rangeLow`	Yes	Lowest comfortable note, as a note name like "D3" or a raw MIDI number.
`rangeHigh`	Yes	Highest comfortable note, as a note name like "C5" or a raw MIDI number.
`voiceType`	No	Optional voice type hint (soprano, mezzo, alto, tenor, baritone, bass). Inferred from the range when omitted.

Output Schema

TableJSON Schema

Name	Required	Description
`vocalId`	Yes	Human-readable profile label, e.g. "Tenor - Balanced tone".
`rangeLow`	Yes	Lowest comfortable note as MIDI.
`rangeHigh`	Yes	Highest comfortable note as MIDI.
`toneLabel`	No
`voiceType`	Yes
`humProfile`	No	Underlying measurements. Timbre fields stay null until an actual hum recording has been analyzed.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedAug 11, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "humProfile": {
+      "description": "Underlying measurements. Timbre fields stay null until an actual hum recording has been analyzed.",
+      "properties": {
+        "brightnessScore": {
+          "type": [
+            "number",
+            "null"
+          ]
+        },
+        "center": {
+          "type": "integer"
+        },
+        "confidence": {
+          "description": "0-1. Derived from range input alone is around 0.55.",
+          "type": "number"
+        },
+        "high": {
+          "type": "integer"
+        },
+        "low": {
+          "type": "integer"
+        },
+        "pitchStability": {
+          "type": "number"
+        },
+        "timbreConfidence": {
+          "type": "number"
+        },
+        "timbreLabel": {
+          "type": "string"
+        },
+        "warmthScore": {
+          "type": [
+            "number",
+            "null"
+          ]
+        }
+      },
+      "type": "object"
+    },
+    "rangeHigh": {
+      "description": "Highest comfortable note as MIDI.",
+      "type": "integer"
+    },
+    "rangeLow": {
+      "description": "Lowest comfortable note as MIDI.",
+      "type": "integer"
+    },
+    "toneLabel": {
+      "type": "string"
+    },
+    "vocalId": {
+      "description": "Human-readable profile label, e.g. \"Tenor - Balanced tone\".",
+      "type": "string"
+    },
+    "voiceType": {
+      "type": "string"
+    }
+  },
+  "required": [
+    "vocalId",
+    "rangeLow",
+    "rangeHigh",
+    "voiceType"
+  ],
+  "type": "object"
+}

First observedAug 11, 2026

TDQS

A4.7/5.0

Behavior5/5

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

Annotations declare readOnly and idempotent, and the description adds context by noting the profile is 'normalized' and 'persistent', and that it is reusable. This clarifies that the tool transforms input into a stable, shareable profile, complementing the annotation-level safety information.

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?

The description is two sentences with no fluff: first sentence defines the function, second provides usage timing. It is front-loaded with the core purpose and ends with actionable guidance.

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?

With a complete input schema, an output schema, and comprehensive annotations, the description does not need to explain return values. It adds the essential workflow context and is fully self-contained for an agent to decide when to invoke it.

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?

Input schema covers all three parameters with detailed descriptions (e.g., 'Lowest comfortable note, as a note name like "D3" or a raw MIDI number'). The description does not add parameter-specific meaning beyond the schema, which is acceptable given 100% schema coverage.

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 action: 'Turn a singer's vocal range into a normalized HumMatch vocal profile' and identifies the output components (Vocal ID, voice type, tone label). It clearly differentiates this tool from sibling tools, which focus on song fitting and recommendations, by being a profile-building prerequisite.

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?

Explicitly instructs when to use: 'Call this first when you know someone's range and want a profile to reuse across the other HumMatch tools.' This provides both a trigger condition and a contrast with alternative tools, establishing this as the initial step in a workflow.

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

All HumMatch tools Inspect

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

Need Help?