Skip to main content
Glama
qobuz-mcp
by cheubes

List Awards

list_awards
Read-only

List press awards and the publications granting them, so you can browse distinctions and then fetch an award's albums or related stories.

Instructions

List press awards and distinctions, with the publication that grants them.

Use get_award for an award's albums, and list_related_stories for its stories.

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": "list_awards"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoNumber of items to return, 1 to 100.
offsetNoNumber of items to skip, to fetch next pages.

Output Schema

NameRequiredDescriptionDefault
itemsYes
limitYes
totalYes
offsetYes
has_moreYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the agent knows this is a safe, non-destructive read against an open catalog. The description adds only the fact that each result carries its granting publication, which is largely covered by the existing output schema; pagination limits and ordering are not discussed.

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 short sentences, front-loaded with the resource being listed and followed by the two sibling cross-references. Nothing is redundant or 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 simple paginated list tool with full schema coverage, annotations, and an output schema, the description supplies what the structured fields cannot: scope and sibling routing. The only real gap is any notion of ordering or total-count behavior, which the output schema likely covers.

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 description coverage is 100% and both parameters (limit, offset) carry bounds and defaults in the schema, so the description does not need to restate them. It adds no semantic nuance beyond the schema, which is the baseline case.

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 a specific verb and resource ('List press awards and distinctions') and adds the notable return detail that each award includes its granting publication. It also names the sibling tools that cover adjacent needs, so an agent can distinguish it from get_award and list_related_stories without inspecting either schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Guidance is explicit about routing: use get_award for an award's albums and list_related_stories for its stories, which is exactly the ambiguity an agent would face. What's missing is a statement of when this tool itself is preferred (e.g., browsing all awards vs. searching), but the context is clear enough to act on.

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