Skip to main content
Glama

pokeapi-mcp-server

by io.github.cyanheads

Get Move

pokeapi_get_move
Read-onlyIdempotent

Get move details by name or numeric ID — type, damage class, power, accuracy, PP, priority, target, stat changes, status-effect chance, and full English effect text. Set include_learners=true to include the list of Pokémon that can learn the move. Move names are available from pokeapi_get_pokemon when include_moves=true.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
identifierYesMove name in lowercase hyphenated form (e.g. "flamethrower", "close-combat") or numeric ID as a string.
include_learnersNoInclude the list of Pokémon that can learn this move. Defaults to false as the list can be large.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
idNoMove ID.
ppNoBase PP. Null when unavailable.
nameNoMove name in hyphenated lowercase.
typeNoElemental type (e.g. "fire").
errorNoPresent when the call failed. Absent on success.
powerNoBase power. Null for status moves.
targetNoTarget selection (e.g. "selected-pokemon", "all-opponents").
accuracyNoAccuracy percentage (0–100). Null for moves that always hit.
priorityNoPriority bracket (positive = higher priority, negative = lower).
effectTextNoFull English effect description. Null when unavailable.
damageClassNoDamage class: physical, special, or status. Null when unavailable.
statChangesNoStat stage changes caused by this move.
effectChanceNoSecondary effect chance percentage. Null when not applicable.
shortEffectTextNoShort English effect summary. Null when unavailable.
learnedByPokemonNoPokémon names that can learn this move (populated when include_learners=true).

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already cover safety (readOnlyHint, idempotentHint, openWorldHint). The description adds valuable behavioral context beyond annotations: the performance warning that include_learners defaults to false because the list can be large, and clarifies that the tool returns full English effect text. No contradiction.

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

Conciseness5/5

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

Three dense sentences: the first front-loads the primary function and returned fields, the second explains the optional flag with a rationale, and the third gives a sourcing hint. No redundancy or wasted words.

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

Completeness5/5

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

Given a simple identifier-only query, an output schema that documents return values, and annotations for safety, the description covers purpose, parameter behavior, and identifier sourcing. An agent has everything needed to call it correctly.

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

Parameters3/5

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

Schema description coverage is 100% and both parameters are well-documented (identifier format, include_learners default). The description adds no new meaning beyond reinforcing the identifier format and the include_learners behavior, so baseline 3 is appropriate.

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?

States a clear verb-resource pair (get move details) and enumerates the specific fields returned (type, damage class, power, accuracy, etc.). It also differentiates from siblings by noting that move names can be obtained from pokeapi_get_pokemon, so the agent knows this is the dedicated move-detail getter.

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

Usage Guidelines4/5

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

Implicitly states when to use: to fetch details for a specific move. It also directs the agent to pokeapi_get_pokemon as the source of move names, aiding workflow. Lacks an explicit 'use X instead' or when-not statement, but the resource distinction from sibling get_* tools is self-evident.

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