Skip to main content
Glama

discogs_status

Verifies your Cotlet.dev account, available credits, and Discogs connection so you can confirm everything is ready before using Discogs tools.

Instructions

Check that your Cotlet.dev account and Discogs are ready: account, credits and Discogs connection.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

A3.5/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 burden, and it does disclose the three things the check inspects (account, credits, Discogs connection), which is real information beyond the name. However, it says nothing about the outcome representation (per-item pass/fail vs a single boolean), whether it performs live network calls to Discogs, or whether it is purely read-only. These gaps matter for a diagnostic tool.

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, and the scope list is placed where it is most useful. There is slight redundancy between 'ready' and the colon-delimited list of the same items, which keeps it from a 5.

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?

The tool is simple (zero parameters, no nesting) but returns no output schema, so the description is the only place an agent could learn what a status check yields. It names the checked domains but not the response shape or failure signalling, leaving a meaningful hole for a diagnostic tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool takes zero parameters, so there is nothing for the description to disambiguate; the schema is already complete with additionalProperties=false. Baseline for a no-parameter tool applies, with no misdescription of inputs.

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?

Uses a specific verb ('Check') with a concrete scope: Cotlet.dev account, credits, and the Discogs connection. This clearly separates it from the action-oriented siblings (open, click, type, read, close, guide), which are interaction tools rather than a readiness check. It stops short of a 5 because the 'ready' framing is vague about whether it validates, reports, or repairs state.

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?

Usage is only implied: an agent can infer this is a pre-flight/verification tool to call before doing Discogs work. The description never states when to call it, when not to, or names an alternative for diagnosing a failed connection. No prerequisites or ordering guidance are given.

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