Pokedex MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| --ttl | No | Cache TTL in milliseconds (default: 600000) | |
| --repo | No | GitHub repository owner/name (default: alexverdin/llm-pokedex-demo) | |
| --branch | No | Git branch (default: main) |
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
} |
| resources | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_pokedex_entriesA | Parse INDEX.md and return all entries as [{ id, name, types, file }]. Optional case-insensitive substring filter on type. |
| search_by_nameA | Return entries whose name contains the query (case-insensitive substring). |
| get_pokemonA | Get an entry by id (e.g. "025") or name (e.g. "pikachu"). Returns parsed data by default; use format to include raw Markdown. |
| get_base_statsA | Return { hp, attack, defense, spAtk, spDef, speed, total } as numbers for an id or name. |
| compare_pokemonA | Compare 2–6 entries. Returns a Markdown table of types + all base stats. |
| rank_by_statA | Rank all 25 entries by a base stat. order defaults to desc, limit defaults to 5. |
| get_evolution_chainA | Return the Evolution section text for an id or name, plus related entries (other Pokémon whose Evolution text mentions this one, and any names this entry mentions). |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| pokedex-index | Raw INDEX.md content (the full lookup table). |
TDQS
Scored across 7 tools
Each tool has a clearly distinct purpose: search by substring, retrieve full entry, retrieve stats, compare multiple, rank by stat, get evolution chain, and list entries with optional type filter. No two tools target the same operation, so selector confusion is unlikely.
All tool names follow a consistent verb_noun pattern (search_by_name, get_pokemon, get_base_stats, compare_pokemon, rank_by_stat, get_evolution_chain, list_pokedex_entries). Naming is uniform and predictable across the entire set.
Seven tools is well-scoped for a focused Pokedex server, covering the core data access needs without unnecessary bloat. Each tool provides a distinct useful capability, fitting comfortably within the ideal 3–15 range.
The tool surface covers the full read-only lifecycle of the Pokedex domain: listing, searching, retrieving, detailed stats, comparisons, rankings, and evolution chains. There are no obvious dead ends or missing fundamental operations for the apparent scope (a 25-entry dataset).