Pokemon TCG Card Search MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| pokemon-card-searchC | Searches for Pokemon cards |
| pokemon-card-priceC | Look up the current market price for a Pokemon card |
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 2 tools
The two tools have clearly distinct purposes: one searches for cards, while the other looks up prices for cards. There is no overlap in functionality, making it easy for an agent to choose the right tool based on the task.
Both tool names follow a consistent pattern of 'pokemon-card-' prefix followed by a descriptive action (search, price). This uniformity makes the tools predictable and easy to understand.
With only two tools, the server feels thin for a card search domain. It lacks operations like filtering, sorting, or detailed card information retrieval, which are typical for such a purpose, making the scope incomplete.
The tool set is severely incomplete for a Pokemon TCG card search server. It covers basic search and price lookup but misses essential operations such as filtering by attributes (e.g., type, rarity), getting card details, or managing collections, leading to potential agent failures.