pokemon-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
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_pokemonB | Get information about a specific Pokemon |
| get_pokemon_speciesC | Get species information about a specific Pokemon |
| get_pokemon_typeC | Get information about a specific Pokemon type |
| get_moveA | Get information about a specific Pokemon move |
| get_ability | Get information about a specific Pokemon ability |
| get_evolution_chain | Get evolution chain information |
| search_pokemonC | Search for Pokemon by name |
| get_pokemon_listB | Get a paginated list of Pokemon |
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 6 tools
Each tool targets a distinct resource: Pokemon, species, type, move, search, and list. There is no overlap, and descriptions clearly differentiate them.
All tools follow a consistent verb_noun pattern with underscores, predominantly using 'get_' (5 of 6) and one 'search_'. No mixing of conventions.
6 tools is well-scoped for a Pokemon information API, covering essential lookups without being excessive or inadequate.
Covers core Pokemon queries (by ID/name, species, type, move) and includes search and listing. Missing advanced features like abilities or evolution chains, but the set feels complete for common use cases.