Skip to main content
Glama
rekordcloud

sonovault-mcp

Official
by rekordcloud
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Label releases

get_label_releases

Retrieve a label's releases, newest first, including the artist for each release. Filter by inclusive date range, or use the same from and until dates to see a single day's releases.

Instructions

A label's releases, newest first, with artist per release. Cursor-paginated. Optional from/until (YYYY-MM-DD, inclusive) limit it to a release-date range; pass the same day for both to see what the label released that day.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
fromNoOnly releases dated on or after this day (YYYY-MM-DD)
limitNo
untilNoOnly releases dated on or before this day (YYYY-MM-DD)
cursorNo
label_idYesSonoVault label ID (from search_labels)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.2.0
    • addedInput schema / properties / from
      Added value: +{
+  "description": "Only releases dated on or after this day (YYYY-MM-DD)",
+  "pattern": "^\\d{4}-\\d{2}-\\d{2}$",
+  "type": "string"
+}
    • addedInput schema / properties / until
      Added value: +{
+  "$ref": "#/properties/from",
+  "description": "Only releases dated on or before this day (YYYY-MM-DD)"
+}
  2. First observedv1.0.2

TDQS

A4/5.0
Behavior3/5

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

The description mentions it is cursor-paginated and includes an 'artist per release', which are useful behavioral details. Since no annotations are provided, these disclosures help. However, it doesn't mention what happens if no releases match, potential rate limits, or whether it supports only the given label or also sublabels. The description is decent but could add more edge-case behavior.

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 a single sentence that packs in the key details: sorting, pagination, date filter, and the same-day example. It is front-loaded with the main purpose and uses no filler words. Every clause adds value.

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 the tool is a paginated list endpoint, the description covers sorting, pagination, and date filtering, which are the main usage points. It lacks explicit return format details, but since no output schema exists, the description could have mentioned that it returns releases with artist info, which it does. The main missing piece is what the 'artist' field contains (e.g., artist name vs ID), but that might be inferred from the schema of other tools. Overall, reasonably complete.

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 schema covers 60% of parameters, and the description adds context for the from/until parameters by explaining the inclusive date range and the same-day use case. It also clarifies that the returned data includes artist per release, which maps to the schema but isn't explicitly documented. For the limit and cursor parameters, it only mentions 'cursor-paginated', so it partially compensates for the schema gaps.

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 clearly states the tool returns a label's releases, newest first, with the artist per release. It distinguishes itself from siblings like get_artist_releases and search_releases by specifying it operates on a label and includes a release date filter. The verb 'get' and resource 'label releases' are specific and unambiguous.

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 explains the optional from/until date range and even gives a concrete use case (pass same day for both to see releases on a specific day). However, it doesn't explicitly mention when to use this vs search_releases or get_artist_releases, so some inference is needed. It does imply the tool is for label-scoped browsing.

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