Pokémon MCP Server
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 |
|---|---|
| get_pokemon_statsB | ポケモンの基礎ステータス（HP、こうげき、ぼうぎょ、とくこう、とくぼう、すばやさ）を取得 |
| get_pokemon_imagesB | ポケモンのスプライト画像（前面、後面、色違い、公式アートワーク）を取得 |
| get_pokemon_infoC | ポケモンの完全な情報（ステータス、画像、基本情報）を取得 |
| get_pokemon_cryB | ポケモンの鳴き声音声ファイルのURLを取得 |
| play_pokemon_cryC | ポケモンの鳴き声を再生（音声ファイルをダウンロードして情報を返す） |
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 5 tools
The tools have some overlap in purpose, particularly between get_pokemon_cry and play_pokemon_cry, which both handle Pokémon cries, and get_pokemon_info and get_pokemon_stats, where stats are a subset of info. However, the descriptions clarify distinctions like URLs vs. playback for cries, and full info vs. just stats, helping agents differentiate.
All tool names follow a consistent verb_noun pattern with 'get_' or 'play_' prefixes and descriptive suffixes like '_cry', '_images', '_info', and '_stats'. This uniformity makes the set predictable and easy to understand.
With 5 tools, the count is reasonable for a Pokémon-focused server, covering key aspects like info, stats, images, and cries. It's slightly under-scoped as it lacks tools for broader operations like searching or listing Pokémon, but it's well-focused on retrieval tasks.
The server covers retrieval of Pokémon data (info, stats, images, cries) but has notable gaps: there are no tools for creating, updating, or deleting data, and no search or listing capabilities. This limits agents to read-only operations, which may be insufficient for interactive use cases.