Skip to main content
Glama
Sign In
sonovault-mcp

sonovault-mcp

Official
by rekordcloud
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Look up a track by ISRC

lookup_isrc

Retrieve full metadata for a music recording by its ISRC, including BPM and musical key. Use it to identify a track and get tempo and key data from SonoVault.

Instructions

Exact lookup of a recording by its ISRC (International Standard Recording Code, e.g. GBDUW0000053). Returns the track's full metadata, including BPM and musical key. Tempo and key: bpm (full tempo, e.g. 123) and musical key in three notations: key_alphanumeric (e.g. '10B'), key_musical (e.g. 'D', 'F#m') and key_open (Open Key, e.g. '3d'), plus keys[] with one entry per source. All null (keys empty) when the track has not been analysed.

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": {
      "isrc": "<isrc>"
    },
    "name": "lookup_isrc"
  }
}

Input Schema

NameRequiredDescriptionDefault
isrcYesISRC code, e.g. GBDUW0000053

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.2

TDQS

A3.8/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does real work: it discloses the returned fields, the three key notations, and explicitly that all tempo/key values are null when a track is unanalysed. It omits not-found/error behavior and whether the lookup is case-sensitive, which are the remaining gaps.

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?

Purpose comes first in a single tight clause, then return-value detail. The enumeration of key_alphanumeric/key_musical/key_open is dense but each item maps to a real returned field, so nothing is wasted.

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

Completeness4/5

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

There is no output schema, and the description compensates by describing the returned metadata and the null-key convention. Only failure modes (invalid or unknown ISRC) are left unaddressed for a tool this simple.

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 is fully documented in the schema (100% coverage) including an example, so the baseline is 3. The description repeats the example format but adds no new constraint or validation detail beyond the schema.

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 first clause gives a specific verb and resource: 'Exact lookup of a recording by its ISRC', with an example code. It implicitly contrasts with search_tracks via the word 'exact', but never names the sibling tools it should be chosen over.

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?

Usage is only implied: an agent can infer this is for known-ISRC lookups rather than fuzzy search, but the description never states when to prefer it over search_tracks, get_track or resolve_tracks, nor what to do when the ISRC is unknown.

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

Deploy Server

Other Tools