Skip to main content
Glama

discogs_info

Read-only

Check Discogs connector status and settings, including version, enabled toolsets, writes, rate-limit state, cache TTL, attribution, and terms notes; optionally retain image URLs.

Instructions

Connector status: version, enabled toolsets, writes, rate-limit state, cache TTL, attribution, and a terms note. Always on.

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_info"
  }
}

Input Schema

NameRequiredDescriptionDefault
include_image_urlsNoIf true, keep image URL strings (images, thumb, cover_image, avatar_url). URLs are never fetched. Default false drops those fields.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, openWorldHint=true, and destructiveHint=false, so the safety profile is covered. The description adds useful context by naming the metadata actually returned (rate-limit state, cache TTL, attribution, terms note), but ambiguous items like 'writes' are never explained and no latency, auth, or response-shape notes are given.

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?

A single compact sentence with the payload list front-loaded and no filler. The trailing 'Always on.' is terse to the point of ambiguity and is the only wasted phrase.

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 no output schema, the description carries the return-value burden and does so by enumerating the status fields, which is appropriate for a one-optional-param read-only tool. The remaining gap is the absence of any usage condition, which matters little for a status endpoint.

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 the single optional boolean (include_image_urls) is fully documented in the schema, including the default-false drop behavior. The description adds nothing about it, so the baseline 3 applies — the schema does all the work here.

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 specifies the resource precisely: it enumerates the connector-status payload (version, enabled toolsets, writes, rate-limit state, cache TTL, attribution, terms note). This is clearly distinguishable from the data-oriented siblings (collection, database, lists, user, wantlist), though it names no verb beyond the implied 'report'.

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 or when-not-to-use guidance. 'Always on' reads as availability of the toolset rather than a condition for invoking the tool, and no alternative or prerequisite is mentioned.

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