Skip to main content
Glama

pokeapi-mcp-server

by io.github.cyanheads

Get Pokémon

pokeapi_get_pokemon
Read-onlyIdempotent

Get a fully denormalized Pokémon dossier in a single call — base stats, types, abilities (with full English effect text), height/weight, resolved evolution chain, sprite URLs including official artwork, species flavor text, variety list, capture rate, growth rate, gender rate, legendary/mythical flags, egg groups, and (optionally) a summarized learnable-move list. Accepts a name (lowercase, hyphens for spaces, e.g. "bulbasaur", "mr-mime") or Pokédex number. Set include_moves=true to include the move summary (large); defaults to false. Use game_version to select flavor text from a specific game (e.g. "sword", "red"); falls back to the most recent English entry when the version is not found. Use pokeapi_find_pokemon to discover Pokémon by type, generation, or egg group before calling this tool.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
identifierYesPokémon name (lowercase hyphenated, e.g. "bulbasaur", "mr-mime") or Pokédex number as a string (e.g. "1", "25").
game_versionNoPokéAPI version name to filter flavor text (e.g. "sword", "red", "scarlet"). Falls back to the most recent English entry when the version is not found.
include_movesNoInclude the full learnable-move summary. Defaults to false because the list is large (100–200+ moves).

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
idNoNational Pokédex number.
nameNoCanonical Pokémon name in hyphenated lowercase.
errorNoPresent when the call failed. Absent on success.
genusNoEnglish genus (e.g. "Seed Pokémon"). Null when unavailable.
movesNoLearnable moves (populated when include_moves=true, empty otherwise).
statsNoBase stats.
typesNoType names ordered by slot (e.g. ["fire", "flying"]).
spritesNoSprite URLs.
heightDmNoHeight in decimetres.
weightHgNoWeight in hectograms.
abilitiesNoAbilities with full effect text.
eggGroupsNoEgg group names.
moveCountNoTotal number of learnable moves regardless of include_moves.
varietiesNoAll forms and variants of this species.
genderRateNoGender ratio: -1 genderless, 0 always male, 8 always female, 1–7 fraction (eighths) female.
generationNoGeneration introduced (e.g. "generation-i").
growthRateNoGrowth rate name (e.g. "medium-slow").
isMythicalNoTrue for mythical Pokémon.
captureRateNoBase capture rate (0–255).
isLegendaryNoTrue for legendary Pokémon.
evolutionChainNoEvolution tree rooted at the base species.
speciesFlavorTextNoFlavor text from the selected (or most recent) game version. Null when none available.

TDQS

A4.5/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare readOnlyHint, openWorldHint, and idempotentHint, so the description builds on that by adding behavioral details: 'fully denormalized' output, the fallback to the most recent English entry when a game version is missing, and the size rationale for include_moves. No contradiction, though it doesn't mention error handling—not required given annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single dense paragraph, but every sentence is informative. It front-loads the main purpose and then covers parameters and alternatives. Could be broken into bullet points for readability, but it's not wasteful or tangential.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's complexity, an existing output schema, and rich annotations, the description covers the core functionality, parameter guidance, and the pointer to the sibling discovery tool. It doesn't explicitly address error cases or limits, but those are not critical for an agent to call the tool correctly, especially with the output schema present.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so baseline is 3, but the description adds real value: it specifies the identifier format with examples ('bulbasaur', 'mr-mime'), explains the default for include_moves and its large size, and clarifies game_version fallback behavior. This exceeds what the schema alone provides.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states a specific verb ('Get') and resource ('Pokémon') while enumerating the returned data fields in detail. It explicitly differentiates from the sibling pokeapi_find_pokemon by noting that discovery is handled there, making the tool's purpose unambiguous.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly instructs to use pokeapi_find_pokemon for discovery by type, generation, or egg group before calling this tool, providing a clear when-not and alternative. It also explains parameter behavior (include_moves default, game_version fallback), leaving no ambiguity about usage.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All pokeapi-mcp-server toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.4/5.0
Disambiguation5/5

Each tool maps to a distinct entity—Pokémon, ability, item, move, nature, or type matchup—with no overlap. pokeapi_find_pokemon serves as a discovery filter, while pokeapi_get_pokemon retrieves full details, making their roles unambiguous.

Naming Consistency5/5

All tools share the consistent pokeapi_ prefix and follow a clear verb-noun pattern: get_<resource> for retrieval and find_pokemon for search. The convention is uniform and predictable across the entire set.

Tool Count5/5

With 7 tools, the server is well-scoped for a Pokémon data API. Each tool covers a core data type without redundancy, and the count is neither too sparse nor overwhelming for agents to navigate.

Completeness4/5

The set covers the primary Pokémon domain—individual Pokémon, abilities, items, moves, natures, and type matchups—plus discovery via filters. Minor gaps exist (e.g., no dedicated berry or encounter tools), but core workflows like team-building and battle analysis are fully supported.

Resources