Skip to main content
Glama

discogs_guide

Get step-by-step guidance on navigating Discogs screens and sign-in to search records, manage collections and wantlists, read inventory, and update seller orders. Call this first for any Discogs task.

Instructions

How to work in Discogs (search records, manage collections and wantlists, read inventory and update seller orders): its screens and the sign-in link. Call this first.

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

Input Schema

NameRequiredDescriptionDefault
taskNoWhat you want done in Discogs, in your words.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations, the description carries the full disclosure burden. It does signal that the output is informational (screens and a sign-in link) rather than an action, but it never states that the tool performs no mutations, does not authenticate, or how the returned guidance is shaped.

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 compact sentence plus a short imperative; every clause maps to a covered capability. The most actionable instruction ('Call this first') sits last rather than being front-loaded.

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

Completeness3/5

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

For a one-optional-parameter, no-output-schema orientation tool, the description covers scope and sequencing adequately. It leaves open what the agent actually receives (static overview vs. task-tailored guidance) and what to do immediately after, which matters for a 'first step' tool.

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 'task' parameter is already documented in the schema as free-form intent. The description adds no information about how the task string influences the returned guidance or whether omitting it changes behavior, so the baseline of 3 applies.

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 domain (Discogs) and enumerates the covered tasks — searching records, managing collections and wantlists, reading inventory, updating seller orders — plus what content it delivers (screens and sign-in link). It is clear this is an orientation/guide tool, though the framing is a topic list rather than a verb+resource pair.

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?

The closing instruction 'Call this first' gives an explicit ordering rule relative to the sibling action tools, which is exactly the guidance an agent needs for an orientation tool. It stops short of saying when the guide is unnecessary or what to do after reading it.

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