Skip to main content
Glama

discogs_click

Clicks a numbered element on the current Discogs page, letting AI agents interact with listings, controls, or navigation after reading available elements.

Instructions

Click a numbered element on the current Discogs page.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "element": "<element>"
    },
    "name": "discogs_click"
  }
}

Input Schema

NameRequiredDescriptionDefault
elementYesElement number from the last read.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

B3.1/5.0
Behavior2/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 says nothing about whether a click navigates away, submits a form, mutates server state, is reversible, or what happens if the element number is stale or out of range — the most important risks for a browser-driving click.

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, front-loaded sentence with no filler; the action and target appear in the first few words. It is efficient rather than padded, though its brevity contributes to the gaps in the other dimensions.

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

Completeness2/5

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

This is a state-changing interaction tool with no annotations and no output schema, meaning the description is the only place to explain sequencing, side effects, and failure modes. It supplies none of that, leaving an agent able to guess the mechanics but not the consequences of a click.

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 coverage is 100% and the sole parameter already documents 'Element number from the last read', with a minimum of 1. The description echoes that meaning ('numbered element on the current page') without adding format, staleness, or invalidation guidance, so the baseline 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?

States a concrete verb (click) and a concrete target (a numbered element on the current Discogs page), which is immediately actionable. It does not, however, distinguish itself from siblings such as discogs_read or discogs_type, so an agent must infer the boundary on its own.

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?

The phrase 'numbered element' and the schema note 'from the last read' imply this is used after a read that surfaces numbered elements. There is no explicit when-to-use/when-not guidance, no statement about pairing with discogs_read first, and no mention of when discogs_type or discogs_guide would be the better choice.

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