Skip to main content
Glama

Discogs

by io.github.pipeworx-io

Recall

recall
Read-onlyIdempotent

Retrieve a value previously saved via remember, or list all saved keys (omit the key argument). Use to look up context the agent stored earlier — the user's target ticker, an address, prior research notes — without re-deriving it from scratch. Scoped to your identifier (anonymous IP, BYO key hash, or account ID). Pair with remember to save, forget to delete.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
keyNoMemory key to retrieve (omit to list all keys)

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "key": "user_research_topic"
+  },
+  {}
+]
  2. First observed

TDQS

A4.9/5.0
Behavior5/5

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

Beyond annotations (readOnlyHint=true, idempotentHint=true, destructiveHint=false), the description adds scoping details, the behavior of listing keys when key is omitted, and mention of pairing with siblings. No contradictions.

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?

Three sentences, each serving a distinct purpose: core action, usage guidance, and scoping/companion tools. No unnecessary words.

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

Completeness5/5

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

Given the simple parameter set, full annotations, and clear sibling relationships, the description provides all necessary context for an agent to use the tool correctly.

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 input schema has 100% coverage for the single parameter 'key' with a description. The tool description adds context about the key's purpose and the behavior when omitted, which is valuable beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description uses the specific verb 'Retrieve' and clearly identifies the resource as 'a value previously saved via remember'. It also explains the dual behavior of retrieving a specific key or listing all keys, distinguishing it from siblings like 'remember' and 'forget'.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly states when to use: 'to look up context the agent stored earlier... without re-deriving it from scratch'. It implies when not to use by describing pairing with 'remember' and 'forget', and notes scoping by identifier.

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

All Discogs toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.6/5.0
Disambiguation1/5

There is severe overlap among tools: ask_pipeworx, ask_pipeworx_beta, and ask_pipeworx_grounded are near-identical variants, and deep_research, discover_tools, and suggest_questions all serve discovery/research purposes. The Discogs-specific tools are distinct, but the large number of redundant Pipeworx tools makes it impossible to tell which one to pick.

Naming Consistency2/5

The Discogs tools follow a clean verb_noun pattern (get_artist, get_label, get_master, get_release), but the majority of the set uses inconsistent, domain-specific names (deep_research, generate_llms_txt, polymarket_arbitrage, scan_competitor_ai_presence). No single naming convention is applied across the server.

Tool Count1/5

With 36 tools, the server is massively over-provisioned for a Discogs-focused API. Most tools (e.g., ask_pipeworx, polymarket_edges, SEC lookups) have nothing to do with Discogs and belong to a separate service. The Discogs surface alone could be served by ~6 tools (search, get_artist, get_label, get_master, get_release, search_within), so the count is wildly inappropriate.

Completeness3/5

For the Discogs domain, the core entities (artist, label, master, release) and full-text search are present, plus semantic search inside records. However, there are gaps like user collections, wantlists, marketplace, and discogs-specific filters beyond format/country. The presence of many unrelated tools does not directly hurt domain coverage, but the Discogs surface is not exhaustive.

Resources