Skip to main content
Glama
Bandcamp MCP Server

Bandcamp MCP Server

bandcamp_status

Verifies that your Cotlet.dev account, credits, and Bandcamp connection are ready so you can manage Bandcamp orders, releases, and messages.

Instructions

Check that your Cotlet.dev account and Bandcamp are ready: account, credits and Bandcamp 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": "bandcamp_status"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

A3.7/5.0
Behavior3/5

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

No annotations exist, so the description carries the full behavioral burden. It usefully enumerates what is inspected (account, credits, connection) — effectively a read-only diagnostic — but does not state that it makes no changes, whether it performs network/auth calls, or how failures are surfaced.

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?

One short sentence with the verb first and the three checked items listed after the colon. No filler, no restating of the tool name.

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

Completeness4/5

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

For a no-parameter, no-output-schema diagnostic, the description covers what is being verified well enough for an agent to decide to call it. A brief note on what a negative result means (e.g., missing credits) would close the remaining gap.

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, which is the baseline-4 case; there is nothing for the description to disambiguate. It correctly does not invent any input requirements.

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 ('Check') and the resources verified (Cotlet.dev account, credits, Bandcamp connection), which clearly separates it from the action-oriented siblings like bandcamp_open, bandcamp_click and bandcamp_read. It reads as a readiness/diagnostic probe, though the word 'status' from the name is never explicitly tied to a returned status object.

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 framing 'check that ... are ready' implies a preflight use before performing Bandcamp actions, but the description never says when to call it, when not to, or that it should precede the other bandcamp_* tools. Usage is inferred rather than stated.

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