Skip to main content
Glama
Sign In
sonovault-mcp

sonovault-mcp

Official
by rekordcloud
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Search tracks

search_tracks

Find tracks in the SonoVault catalog by required artist and title, returning ISRC, genre, duration, BPM, key, credits, and release metadata.

Instructions

Search the SonoVault catalog (93M+ tracks) by artist and title. Both are required; there is no free-text search. Returns ISRC, genre, duration, BPM, musical key, artist credits, and release info (album, label, release date) per track. 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": {
      "artist": "<artist>",
      "title": "<title>"
    },
    "name": "search_tracks"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMax results (default 20)
titleYesTrack title, e.g. 'One More Time'
artistYesArtist name, e.g. 'Daft Punk'

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.2

TDQS

A3.7/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 discloses the read-only search nature, the catalog scale (93M+ tracks), the full set of returned fields, the multi-notation key fields, and the important edge case that all key fields are null when a track has not been analysed. It omits auth, rate limits, and pagination behavior beyond the limit parameter.

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?

Front-loaded with the core verb and constraints, then the payload description. The tempo/key sentence is dense but justified because there is no output schema; every sentence carries information, though it is close to overloaded.

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?

Without an output schema, the description usefully enumerates returned fields, the three key notations, keys[], and the unanalysed-track case. It lacks guidance on zero-result behavior, disambiguation when multiple tracks match, and pagination, which keeps it from full completeness.

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 coverage is 100%, so the schema already documents artist, title, and limit; baseline is 3. The description reinforces that artist and title are mandatory and free-text is unsupported, but adds no new syntax, matching, or limit semantics beyond the schema.

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?

Names a specific verb+resource (search the SonoVault catalog) and constrains it precisely to artist+title with 'no free-text search', which separates it from browse_tracks and resolve_tracks by implication. However, it never names a sibling or routes to one explicitly, so full sibling differentiation is not achieved.

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?

'Both are required; there is no free-text search' defines the input contract and implicitly signals when to use it (when you have an artist and title). It stops short of saying when NOT to use it or which sibling to pick for exploration, ID lookup, or fuzzy matching.

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