Skip to main content
Glama
Sign In
sonovault-mcp

sonovault-mcp

Official
by rekordcloud
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Bulk resolve

resolve_tracks

Resolve up to 100 artist-title pairs, ISRCs, SonoVault IDs, or platform IDs to canonical tracks with cross-platform links, BPM, and musical key in one call.

Instructions

Resolve up to 100 inputs in one call to canonical tracks plus cross-platform links. input_type picks the key: 'track_name' (items are {artist, title} objects), 'isrc', 'sonovault_id', or a platform id type ('spotify_id', 'applemusic_id', 'tidal_id', 'beatport_id', 'discogs_id', 'musicbrainz_id'). A discogs_id item is a Discogs track key (release ID plus track position, e.g. '2844-A'), not a bare release ID. Each matched track carries the same fields as get_track, including BPM and musical key. Costs one API credit per line.

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": {
      "input_type": "<input_type>",
      "items": "<items>"
    },
    "name": "resolve_tracks"
  }
}

Input Schema

NameRequiredDescriptionDefault
itemsYesStrings for id/isrc types; {artist, title} objects for track_name
input_typeYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.2

TDQS

A4.2/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 disclose important behavior: a 100-item cap, one API credit per line, and that matched tracks have the same fields as get_track. It does not say what happens to unmatched items or how partial failures are reported.

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?

Dense and front-loaded: batch size and outcome come first, followed by parameter semantics and the important Discogs edge case. Every sentence contributes useful information with no filler.

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?

Given two parameters, no annotations, and no output schema, the description provides substantial operational context including batch cap, credit cost, and a proxy for the return shape via get_track. It still omits unmatched-item behavior and partial-failure semantics, which are material for a bulk resolver.

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 coverage is only 50%, so the description must add meaning and it does: input_type values are enumerated with their item shapes, and the tricky Discogs key format is called out explicitly. It does not describe format expectations for ISRC or platform ids beyond naming the types, but the critical ambiguity is addressed.

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: bulk-resolve inputs into canonical tracks plus cross-platform links. The batch scope and input-type flexibility distinguish it from single-record siblings like get_track, lookup_isrc, and search_tracks.

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 description makes clear that this is the bulk resolution path and lists the accepted key types, but it never says when to choose this over lookup_isrc, get_track, or search_tracks. Usage is implied by the batch framing rather than explicitly routed.

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