Skip to main content
Glama
Sign In
sonovault-mcp

sonovault-mcp

Official
by rekordcloud
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Cross-platform links

get_platform_links

Resolve any track to its unique ID and deep links on Spotify, Apple Music, Tidal, Beatport, Discogs, MusicBrainz, and YouTube using an ISRC, SonoVault ID, or platform ID.

Instructions

Resolve a track to its ID and deep link on every supported platform: Spotify, Apple Music, Tidal, Beatport, Discogs, MusicBrainz, YouTube. Identify the track by exactly one of: SonoVault id, ISRC, or any platform's ID.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_platform_links"
  }
}

Input Schema

NameRequiredDescriptionDefault
idNoSonoVault track ID
isrcNo
tidal_idNo
discogs_idNoDiscogs track key: release ID plus track position, e.g. '2844-A'. A bare release ID matches nothing.
spotify_idNo
youtube_idNo
beatport_idNo
applemusic_idNo
musicbrainz_idNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.2.1
    • addedInput schema / properties / discogs_id / description
      Added value: +"Discogs track key: release ID plus track position, e.g. '2844-A'. A bare release ID matches nothing."
  2. First observedv1.0.2

TDQS

A3.7/5.0
Behavior3/5

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

With no annotations, the description must carry the transparency burden. It discloses the core behavior—returning the ID and deep link for all listed platforms—and the exactly-one-input requirement. However, it does not describe error cases, behavior when multiple IDs are provided, matching exactness, or any access/rate limits.

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?

Two sentences, with the core resolution behavior front-loaded and the input cardinality rule stated immediately after. Every clause contributes; there is no filler or repetition of schema fields.

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

Completeness3/5

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

The description covers the main invocation rule and the output's overall shape, but with no output schema and no annotations it should also clarify the response structure and error behavior for missing/ambiguous identifiers. The schema's all-optional parameters also conflict slightly with the description's 'exactly one' rule, leaving room for misuse.

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 description coverage is only 22%, so the description needed to compensate. It does add the key meaning that all listed platform parameters are valid lookup keys and that exactly one must be supplied, but it leaves most platform ID formats undefined beyond the schema's Discogs note.

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 description names a specific action ('Resolve a track to its ID and deep link') and lists the seven supported platforms, so an agent knows what the tool returns. It does not explicitly differentiate itself from sibling tools such as resolve_tracks, which likely overlaps in behavior, so it misses the top score.

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

Usage Guidelines4/5

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

It gives a clear, explicit usage rule: identify the track by exactly one of SonoVault id, ISRC, or any platform ID. It does not mention when to prefer this tool over resolve_tracks, lookup_isrc, or get_track, so it lacks explicit alternatives and exclusions.

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