Skip to main content
Glama
rekordcloud

sonovault-mcp

Official
by rekordcloud
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Get release with tracklist

get_release

Fetch a music release by ID to view its full tracklist with ISRCs, plus edition details like label, format, and catalog number. Pass an edition ID to see that edition's track numbering.

Instructions

Fetch one release by SonoVault release ID, including its full tracklist with ISRCs. Tracks come back in playing order, each with disc_number and track_number; a track whose position is unknown sorts last with both null. A SonoVault release groups every edition of an album onto one record, so the response also carries an editions array naming the real editions behind it, each with its provider, format, release date, barcode, country, track count, label and catalog number (pressings of one album often carry different labels); pass one of their ids as edition to render that edition's numbering instead of the default consensus. musicbrainz_release_ids and musicbrainz_release_group_ids are arrays for the same reason.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesSonoVault release ID
editionNoEdition id from the response's editions array. Renders that edition's track numbering; tracks it does not carry keep a null position and come last.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.1.0
    • addedInput schema / properties / edition
      Added value: +{
+  "description": "Edition id from the response's editions array. Renders that edition's track numbering; tracks it does not carry keep a null position and come last.",
+  "type": "integer"
+}
  2. First observedv1.0.2

TDQS

A4.8/5.0
Behavior5/5

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

With no annotations, the description carries the full behavioral burden and does so thoroughly: it explains track ordering, null-position handling for unknown track numbers, the multi-edition aggregation model, the meaning of the editions array and its fields, the edition parameter's renumbering effect, and the reason the MusicBrainz ID fields are arrays. This goes well beyond the schema.

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 long but information-dense and logically structured: main fetch operation first, then tracklist ordering, then the editions/edition parameter explanation, then the MusicBrainz arrays. Every sentence contributes necessary domain context or parameter behavior; there is no filler.

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?

Given there is no output schema, the description supplies what the agent needs to interpret the response: track fields, edition fields, and ID arrays. It also defines the domain-specific behavior of the optional edition parameter. No critical invocation detail appears to be missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is already 100%, but the description adds real meaning: it explains that editions are aggregated onto one record, that passing an edition id swaps the default consensus numbering for that edition's numbering, and how tracks missing from an edition are placed. The id parameter's role is also clearly stated as the SonoVault release ID.

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 a specific verb ('Fetch'), an exact target ('one release by SonoVault release ID'), and the key delivered content ('full tracklist with ISRCs'). This clearly separates it from sibling tools that list releases by artist or label, search releases, or retrieve single tracks.

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 clear context: use this when you already have a SonoVault release ID and need the release plus tracklist/edition data. It does not explicitly name alternatives or say when not to use it, but the direct-by-ID phrasing is enough to disambiguate from the search/list siblings.

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