Skip to main content
Glama

tcgdata.dev — European TCG Prices

List supported games

list_games
Read-onlyIdempotent

List the five supported game identifiers and catalogue languages. Static API capabilities, no API request or account usage.

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": "list_games"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
gamesYes
requests_chargedYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / properties / games / items / properties / id / enum
      Previous value: -[
      -  "pokemon",
      -  "pokemon_jp",
      -  "magic",
      -  "lorcana",
      -  "onepiece",
      -  "yugioh"
      -]New value: +[
      +  "pokemon",
      +  "pokemon_jp",
      +  "lorcana",
      +  "onepiece",
      +  "yugioh"
      +]
  2. First observed

TDQS

A3.9/5.0
Behavior3/5

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

The annotations already declare readOnlyHint, idempotentHint and openWorldHint=false, so safety and network behavior are covered. The description does add real value beyond them by disclosing that the call is static, consumes no API request or account usage, and returns a fixed set of five games. It says nothing about the returned language catalogue's shape or size, though an output schema covers results.

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?

Two short sentences, zero filler, with the scope decision (five fixed games plus languages) front-loaded before the operational note. Every clause earns its place.

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 zero-parameter, read-only enumeration with an output schema and full annotation coverage, the description gives everything needed to call it correctly. The only soft spot is that "catalogue languages" is not expanded, leaving the agent to rely on the output schema to learn what languages mean.

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 the schema is trivially complete and there is no parameter meaning to convey. Baseline for a no-parameter tool applies; the description correctly stays silent on 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?

States a precise verb and resource ("List the five supported game identifiers and catalogue languages") plus a hard bound of five, so an agent knows exactly what comes back. It doesn't explicitly contrast itself with the card/catalogue siblings, but the static-enumeration framing makes the distinction obvious.

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

Usage Guidelines4/5

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

"Static API capabilities, no API request or account usage" tells the agent this is a free, quota-free discovery call worth making before other calls. It stops short of naming explicit alternatives or exclusions, so it is clear context rather than full when/when-not guidance.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources