Skip to main content
Glama
qobuz-mcp
by cheubes

Get Award

get_award
Read-only

Retrieve a Qobuz press award and its winning albums, optionally filtered by genre, with pagination via limit and offset.

Instructions

Get a press award and the albums that received it, optionally for one genre.

The albums are paginated with limit and offset; albums.has_more tells whether more albums exist.

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": {
      "award_id": "<award_id>"
    },
    "name": "get_award"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoNumber of items to return, 1 to 100.
offsetNoNumber of items to skip, to fetch next pages.
award_idYesQobuz award ID, from `list_awards`.
genre_idNoOnly items of this genre (an ID from `list_genres`).

Output Schema

NameRequiredDescriptionDefault
idYes
urlYes
nameYes
albumsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety is covered; the description adds the meaningful behavioral fact that the album collection is paginated and that albums.has_more signals further pages. That pagination contract is genuinely beyond the annotations, though it partly restates a field the output schema already defines.

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?

Two short sentences, front-loaded with what is returned and followed by the pagination caveat; nothing is padding. The second sentence is slightly redundant with the output schema's has_more field, but it is placed well and cheap to read.

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?

With an output schema and full annotation coverage, the description only needs to cover the interaction contract, which it largely does: what is returned, the optional genre narrowing, and pagination. A note on behavior for an unknown award_id and disambiguation of the genre filter's target are the only real gaps.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3, but the description earns above baseline by clarifying that limit and offset paginate the albums sub-collection rather than the award itself, and that genre_id narrows that collection. It does not resolve the residual ambiguity of whether genre_id filters the award or its albums.

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?

States a specific verb and resource (retrieve a press award) plus the associated payload (the albums that received it) and an optional filter (one genre). This is clearly a single-item detail fetch, distinguishable in spirit from list_awards, but the description never names that sibling to make the split explicit.

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 implied rather than stated: you call it when you need one award's details and its albums, and the genre mention hints at a filtered variant. There is no explicit when-to-use versus list_awards or search_catalog, and no note that award_id must first be obtained via list_awards (that hint lives only in the schema).

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