Pokémon TCG Pocket MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| LANGUAGES | No | Comma-separated list of languages to use (e.g., 'en,de'). Supported values: en, fr, de, es, it, pt-br. | |
| DATABASE_URL | No | The file path to the local card database, e.g. 'file:/absolute/path/to/cards.db'. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_cardsA | Search Pokémon TCG Pocket cards. All fields except |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 1 tool
With only a single tool, there is no possibility of tool confusion or overlap. The tool's purpose is clearly defined and self-contained.
The sole tool uses a clear verb_noun convention ('search_cards'), which is internally consistent. With only one tool, the naming pattern is trivially uniform.
A single tool feels too sparse for a Pokémon TCG Pocket server, which likely expects capabilities like fetching card details, browsing sets, or managing collections. One search tool does not justify a server in most practical contexts.
The server only offers search, with no way to retrieve, compare, or manage specific cards or sets. This leaves significant gaps for any workflow beyond simple card lookup, forcing agents to improvise or fail.