Skip to main content
Glama
rekordcloud

sonovault-mcp

Official
by rekordcloud
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Artist releases

get_artist_releases

Retrieve an artist's releases, newest first, with pagination and optional date-range filtering.

Instructions

An artist's releases, newest first. Use the cursor from a previous call for the next page. Optional from/until (YYYY-MM-DD, inclusive) limit it to a release-date range.

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)
cursorNonext_cursor from the previous page
artist_idYesSonoVault artist ID (from search_artists)

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
Behavior4/5

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

With no annotations, the description carries the behavioral burden. It discloses ordering (newest first), pagination (cursor-based), and date range inclusivity. This is useful and goes beyond the schema. It does not mention edge cases like default limit, cursor staleness, or return format, but the core behavior is transparent.

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 no wasted words. The main purpose is front-loaded, followed by pagination and filtering details. Everything earns its place and is easy to scan.

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?

For a paginated list tool with 5 parameters and no output schema, the description gives the necessary information: purpose, ordering, pagination, and filter semantics. It does not explain default limits or error conditions, but these are less critical for basic invocation. Overall, adequate for correct use.

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 covers 80% of parameters with descriptions. The description's mention of from/until being inclusive and 'release-date range' is mostly redundant since schema already says 'on or after' and 'on or before'. Cursor semantics in the description mirror the schema's 'next_cursor from the previous page'. No significant new parameter meaning added.

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 states exactly what the tool does: it returns an artist's releases, ordered newest first. This clearly distinguishes it from sibling tools like get_label_releases (by artist vs. label) and search_releases (direct listing vs. searching). The resource and scope are unambiguous.

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?

It implies usage context: you need an artist_id and can paginate with a cursor. It also explains how to filter by date range. However, it does not explicitly tell when to choose this over alternatives like search_releases, or when a label-oriented view would be better. Guidance is present but not exhaustive.

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