Skip to main content
Glama

Summarize My Discogs Collection

discogs_collection_summary
Read-only

Summarizes your Discogs collection by showing its size, per-folder copy counts, and Discogs' minimum, median, and maximum value estimates in your account currency.

Instructions

Summarize the Owner's own Discogs Collection: its size and what it is worth.

Shows the number of Copies in the Collection and in each of its folders, with the folder_id for discogs_list_collection, and Discogs' minimum, median and maximum estimate of the Collection's value, as Discogs reports it in the currency of the Owner's Discogs settings. Use discogs_list_collection to see the Copies themselves and discogs_get_prices for the Lowest price of particular Releases.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.7/5.0
Behavior4/5

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

The annotations already declare readOnlyHint=true and openWorldHint=true, so safety is covered. The description adds real behavioral context beyond them: value figures are Discogs' own estimates, denominated in the currency from the Owner's Discogs settings, and folder_id values are returned specifically to feed discogs_list_collection. It does not mention auth/scope requirements, but nothing is contradicted.

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?

Front-loaded with the purpose, then the returned contents, then the sibling routing. Three sentences, each earning its place, with no filler or repetition of the title.

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?

There is no output schema, so the description must describe the return shape — and it does, covering size, per-folder breakdown, folder_id, and the three value estimates plus their currency basis. Nothing an agent needs to call and interpret this zero-parameter read is missing.

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?

The tool takes zero parameters, so the baseline is 4; there is no parameter meaning to add. The description correctly implies no input is needed.

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 (summarize the Owner's own Discogs Collection) and names exactly what the summary contains: copy counts overall and per folder, folder_id values, and Discogs' min/median/max value estimates. It is immediately distinguishable from list-oriented siblings.

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

Usage Guidelines5/5

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

It explicitly routes the agent: use discogs_list_collection to see the Copies themselves, and discogs_get_prices for the Lowest price of particular Releases. That gives both the alternative tools and the conditions that select them.

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