APIbase

PokéAPI — Pokemon Move Details

pokeapi.move.detail

Read-onlyIdempotent

Retrieve detailed Pokémon move data by name or ID, including type, power, accuracy, PP, effects, and battle metadata for game analysis and team building.

Instructions

Get detailed data for any of 900+ Pokemon moves by name or move ID. Returns: type, damage class (physical/special/status), power, accuracy, PP (power points), priority, effect chance, short effect description, full effect text, target scope, generation introduced, and battle metadata (ailment, drain, healing, crit rate, flinch chance). Examples: "tackle" (power 40), "thunderbolt" (power 90, 10% paralysis), "surf" (power 90, hits all adjacent), "swords-dance" (status, raises Attack). Multi-word move names use hyphens: "ice-beam", "fire-blast", "hyper-beam". No auth required; fair-use free API. Source: PokéAPI (pokeapi.co).

Input Schema

Name	Required	Description	Default
`name_or_id`	Yes	Move name (e.g. "tackle", "thunderbolt", "surf") or numeric move ID (e.g. 33). Names use hyphens for multi-word moves (e.g. "ice-beam", "fire-blast").

Output Schema

Name	Required	Description	Default
`error`	No	Present only when the call failed. Includes error code, message, request_id, and any provider-specific extras.
`result`	No	Tool response payload. Shape varies per tool — consult the tool description and inputSchema. May be an object, array, string, or number depending on the upstream provider response.

Schema Changelog

Changes observed during successful MCP inspections.

Addedv2.2.0Oct 29, 2026

TDQS

A4/5.0

Behavior3/5

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint=false, covering safety and side effects. The description adds 'No auth required; fair-use free API,' which is minor behavioral context, and lists return fields, which is useful but not strictly behavioral. It doesn't contradict annotations, so the addition is modest.

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?

The description is informative and well-structured, front-loading the purpose, then listing return fields, and providing concrete examples. It is slightly verbose but each sentence earns its place by clarifying usage or output. No redundancy.

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?

For a single-parameter lookup tool with an output schema present, the description is complete: it specifies the input format (name or ID, hyphenation), enumerates returned fields, gives examples, and notes auth/fair-use. Nothing an agent needs to call it correctly is missing.

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 coverage is 100%: the parameter description already explains name_or_id with examples and hyphenation rules. The description repeats this and adds illustrative examples with power values, but it doesn't add essential meaning beyond the schema. 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?

The description states a specific action (get detailed data) on a specific resource (900+ Pokemon moves) and includes examples that clearly distinguish it from sibling tools like pokeapi.pokemon.detail, which are about Pokemon, species, or type matchups. The scope is unambiguous.

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?

While it doesn't explicitly say 'use this for moves, not for Pokemon details,' the purpose and examples make it clear that this is the tool for move data. It implicitly differentiates from siblings by being move-specific, and the examples reinforce when to call it. It lacks an explicit 'when-not-to-use' but the context is strong.

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

Deploy Server