Skip to main content
Glama
Sign In
sonovault-mcp

sonovault-mcp

Official
by rekordcloud
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Get track by ID

get_track

Fetch a track by SonoVault track ID to retrieve detailed metadata including ISRC, genre, duration, BPM, musical key, artist credits, and releases.

Instructions

Fetch one track by its SonoVault track ID, with full metadata (ISRC, genre, duration, BPM, musical key, artist credits, releases). Tempo and key: bpm (full tempo, e.g. 123) and musical key in three notations: key_alphanumeric (e.g. '10B'), key_musical (e.g. 'D', 'F#m') and key_open (Open Key, e.g. '3d'), plus keys[] with one entry per source. All null (keys empty) when the track has not been analysed.

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": {
      "id": "<id>"
    },
    "name": "get_track"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesSonoVault track ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.2

TDQS

A3.9/5.0
Behavior4/5

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

With no annotations, the description does real work: it enumerates what the response contains (ISRC, genre, duration, BPM, key, credits, releases) and discloses the important edge case that tempo/key fields are null and keys[] is empty for un-analysed tracks. It stops short of covering not-found/error behavior, which is the remaining gap.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Purpose is front-loaded in the first clause, followed by return-detail that earns its place because there is no output schema. The key-notation enumeration is somewhat dense but informative rather than padded.

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 single-parameter read with no output schema, the description carries the return-shape burden well, listing metadata fields and explaining null/key-array semantics. Missing only not-found behavior and any indication of whether the call is read-only/cheap.

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?

Only one parameter (id) with 100% schema description coverage, so the schema already explains it. The description restates 'SonoVault track ID' but adds no format, range, or source guidance beyond that, so the baseline of 3 applies.

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 ('Fetch one track by its SonoVault track ID') and explicitly scopes it to a single record, which distinguishes it from sibling list/search tools like search_tracks and browse_tracks. An agent can identify the operation without opening the schema.

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 phrase 'by its SonoVault track ID' implies a prerequisite (you must already have an ID), which indirectly separates it from search tools, but no alternative is named and no when-not-to-use guidance is given. Usage is inferable but not stated.

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