Skip to main content
Glama

Discogs Search

discogs_search
Read-onlyIdempotent

Full-text search across Discogs (releases, masters, artists, labels). Filter by type, title, artist, format (e.g., "Vinyl", "CD"), country, year, genre, style, label.

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": {
      "query": "The Beatles Abbey Road"
    },
    "name": "discogs_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNo1-based page
typeNorelease | master | artist | label
yearNoRelease year or year-range
genreNoGenre filter
labelNoLabel filter
queryYesFree-text query
styleNoStyle filter
titleNoTitle filter
artistNoArtist filter
formatNoe.g., "Vinyl", "CD", "Album"
countryNoCountry of release
per_pageNo1-100 (default 25)

Output Schema

NameRequiredDescriptionDefault
pageYesCurrent page number (1-based)
totalYesTotal number of matching items across all pages
resultsYesSearch result items
per_pageYesNumber of results per page
returnedYesNumber of results returned in this response
total_pagesYesTotal number of pages available

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.4/5.0
Behavior2/5

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint and destructiveHint=false, so the safety profile is fully covered structurally. The description adds essentially no behavioral context beyond that - it says nothing about result caps, rate limits, or how pagination behaves, which matters for an open-world search over 12 parameters.

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 sentences, front-loaded with the core action and scope, with zero filler. The second sentence largely re-lists fields already present in the schema, which is mild redundancy but aids quick scanning.

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

Completeness5/5

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

With an output schema present and 100% schema description coverage across all 12 parameters, the description only needs to establish scope and available filters - which it does. Nothing essential for a correct first invocation is missing.

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%, so the baseline is 3 and the schema already documents every filter. The description restates the filter names and adds small clarifying examples ("Vinyl", "CD") for format, but contributes no semantics beyond what the schema provides.

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 a specific verb ("Full-text search") and resource ("Discogs") and enumerates the entity types searched (releases, masters, artists, labels). It clearly separates this as a discovery tool from the get-style siblings, though it never explicitly contrasts with discogs_get_release or discogs_get_artist.

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 by "full-text search" plus the filter list, so an agent can infer this is the entry point for finding items by criteria. However, there is no explicit when-to-use, no stated alternative such as using the get tools to fetch full details, and no guidance on paging through large result sets.

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.