Skip to main content
Glama

discogs_read

Reads the current Discogs page and extracts its text, numbered buttons, links, and fields, optionally limited to a specific element.

Instructions

Read the current Discogs page: its text and numbered buttons, links and fields.

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

Input Schema

NameRequiredDescriptionDefault
elementNoRead only inside this element.

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?

No annotations are supplied, so the description carries the full disclosure burden. It implies a non-mutating read and usefully characterizes the returned structure (page text plus numbered buttons/links/fields), but says nothing about scope limits, how much of the page is returned, whether reading alters page state, or any auth/session requirements.

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?

One front-loaded sentence that names the action and then lists exactly what comes back. No filler, no restatement of the tool name.

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?

For a simple one-optional-param read tool with no output schema, the description covers the essentials, including that buttons are numbered, which is the key link to discogs_click. It falls short only on scoping and volume of returned content, which matter because no output schema exists to clarify them.

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?

The single optional parameter is fully documented in the schema ("Read only inside this element"), so the schema already does the work. The description never mentions the element parameter or any scoping behavior, adding no meaning beyond the schema; baseline 3 applies at 100% coverage.

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 uses a specific verb and resource ("Read the current Discogs page") and enumerates the content returned: text, numbered buttons, links and fields. That distinguishes it from siblings like discogs_click or discogs_type, which act on the page, though the description itself never names an alternative.

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?

Use is implied by "the current page" and by the emphasis on reading page structure, which suggests inspection before acting. There is no explicit when-to-use, no prerequisite, and no statement about when reading is unnecessary versus using discogs_status or discogs_guide.

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