Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
COTLET_API_KEYYesAPI key created in the Cotlet.dev console; required for the hosted MCP endpoint (as a bearer token) and for calling the local browser helper tools.

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

Discogs through Cotlet.dev. Call discogs_guide first. Set COTLET_API_KEY (https://cotlet.dev/app).

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": false
}

Tools

Functions exposed to the LLM to take actions

NameDescription
discogs_guideA

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.

discogs_statusA

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

discogs_openB

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.

discogs_readA

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

discogs_clickB

Click a numbered element on the current Discogs page.

discogs_typeC

Type text into a numbered field on the current Discogs page.

discogs_closeA

Close the Discogs browser session when the work is done, so credits stop running.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A3.6/5.0

Scored across 7 tools

Disambiguation4/5

The core browser primitives (open, read, click, type, close) are clearly distinct and map to different actions. The only mild overlap is between discogs_guide and discogs_status, since both are setup-oriented tools, but their purposes remain distinguishable.

Naming Consistency5/5

All tools use the same discogs_ prefix followed by a short lowercase snake_case action or label. The naming is highly predictable and internally consistent.

Tool Count5/5

Seven tools is well-scoped for a browser-driven Discogs automation server. Each tool has a clear role in the session lifecycle or interaction model.

Completeness4/5

The set covers the essential browser lifecycle: guidance, status, open, inspect, click, type, and close. Minor gaps exist for common browser actions like scrolling, going back, selecting dropdowns, or waiting, but most Discogs workflows can likely be handled through the provided primitives.