Skip to main content
Glama
qobuz-mcp
by cheubes

Check Library

check_library
Read-only

Check whether albums, artists, and tracks are in a user's Qobuz favorites, and whether albums and tracks are purchased. Use it to verify library status before acting on saved or purchasable music.

Instructions

Check whether given albums, artists and tracks are in the user's favorites, and whether given albums and tracks are purchased.

Results keep the order of the given IDs. purchased is null for artists.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "check_library"
  }
}

Input Schema

NameRequiredDescriptionDefault
album_idsNo
track_idsNo
artist_idsNo

Output Schema

NameRequiredDescriptionDefault
albumsYes
tracksYes
artistsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior4/5

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

Beyond the readOnly/openWorld annotations, the description supplies two non-obvious behavioral facts: results preserve the order of the input IDs (so responses can be zipped by position), and `purchased` is null for artists. It does not disclose behavior for omitted or empty ID arrays, which is the remaining ambiguity for a batched lookup.

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 tight sentences, front-loaded with the core operation, then the important result-shaping caveats. No filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists, so return-value shape need not be restated, and the ordering/artist-null notes are useful. Still missing for a 3-array batched lookup: default-null semantics for omitted arrays, limits on array size, and whether non-existent IDs appear in the result.

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 already types each array (album IDs as strings, artist/track IDs as integers), and the description's only semantic addition is that artist entries have no purchase field. It says nothing about what happens when an array is omitted (all default to null) or whether results include unknown IDs.

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: checking membership of albums/artists/tracks in favorites and purchase status for albums/tracks. It is distinguishable from list_favorites or list_purchases because it is a lookup over supplied IDs rather than an enumeration, though it never names those siblings explicitly.

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?

Usage is only implied by the phrase 'given albums, artists and tracks' – an agent can infer this is a batch status check for known IDs. There is no explicit when-to-use/when-not guidance, and no direction to list_favorites or list_purchases as alternatives for enumeration.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.