Skip to main content
Glama

discogs_open

Opens a Discogs page in your signed-in Cloud Browser to search records, manage collections and wantlists, inspect inventory, and update seller orders.

Instructions

Open a Discogs page in your signed-in Cloud Browser (default https://discogs.com) to work with search records, manage collections and wantlists, read inventory and update seller orders.

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

Input Schema

NameRequiredDescriptionDefault
urlNoPage to open. Default: https://discogs.com

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

B3.2/5.0
Behavior2/5

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

With no annotations, the description carries the full behavioral burden. It usefully discloses that the browser is the user's signed-in Cloud Browser and that the URL defaults to https://discogs.com, but says nothing about what happens if a page is already open (navigate vs. new tab), whether state is preserved, authentication failures, or what the agent observes after opening.

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 front-loaded sentence with the action and target stated first. The trailing list of use cases is somewhat padded but still informative rather than redundant.

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 simple one-optional-parameter tool with no output schema, the definition covers purpose, target site, and auth context adequately. The remaining gap is session behavior and expected post-open state, which matters because this is the gateway to all sibling tools.

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 single `url` parameter is already documented with its default, so the description's repetition of the default adds only marginal meaning. It provides no guidance on accepted URL forms or non-Discogs destinations.

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 specific verb plus resource ("Open a Discogs page in your signed-in Cloud Browser") and names the default target, so an agent can distinguish it from discogs_click, discogs_read, or discogs_close. It stops short of explicitly contrasting itself with those siblings.

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 clause "to work with search records, manage collections and wantlists, read inventory and update seller orders" implies this is the entry point for any Discogs workflow, but there is no explicit when-to-use/when-not or instruction about when another sibling should be preferred.

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