Skip to main content
Glama

Discogs Get Release

discogs_get_release
Read-onlyIdempotent

Full release detail: title, artists, labels, formats, tracklist, credits, year, country, notes, identifiers (barcode, matrix), data quality.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

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

Input Schema

NameRequiredDescriptionDefault
release_idYesDiscogs release ID

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, openWorld, and non-destructive, so the safety profile is covered. The description adds value by disclosing the breadth and shape of returned content, but says nothing about authentication requirements, rate limits, or behavior for invalid/missing release IDs — relevant for an open-world API tool.

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?

One tight sentence that front-loads the scope ('Full release detail:') and then lists fields with zero filler. It is a fragment rather than a structured sentence, but every token carries information.

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?

The tool is simple (one required ID parameter) and has an output schema, so the description needn't explain return values. Listing the content categories plus the annotations gives an agent enough to call it correctly; only error/edge-case behavior is unaddressed.

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% and the single parameter is already documented as 'Discogs release ID', so the baseline is 3. The description adds no extra meaning about the ID format or where it comes from, but with one fully-described parameter nothing critical is missing.

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?

The description names the specific resource (a Discogs release) and enumerates the fields returned (title, artists, labels, formats, tracklist, credits, identifiers), which clearly separates it from discogs_get_artist, get_label, and get_master. It lacks an explicit verb, so the retrieval action is inferred from the tool name rather than stated.

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

Usage Guidelines2/5

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

There is no when-to-use guidance, no mention of prerequisites (an ID obtained from search), and no reference to alternative tools such as discogs_search for finding an ID or get_master for master releases. Usage is only inferable from the name and single parameter.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.