pokeapi-mcp-server

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

Name	Required	Description	Default
`identifier`	Yes	Move name in lowercase hyphenated form (e.g. "flamethrower", "close-combat") or numeric ID as a string.
`include_learners`	No	Include the list of Pokémon that can learn this move. Defaults to false as the list can be large.

Output Schema

TableJSON Schema

Name	Required	Description
`id`	No	Move ID.
`pp`	No	Base PP. Null when unavailable.
`name`	No	Move name in hyphenated lowercase.
`type`	No	Elemental type (e.g. "fire").
`error`	No	Present when the call failed. Absent on success.
`power`	No	Base power. Null for status moves.
`target`	No	Target selection (e.g. "selected-pokemon", "all-opponents").
`accuracy`	No	Accuracy percentage (0–100). Null for moves that always hit.
`priority`	No	Priority bracket (positive = higher priority, negative = lower).
`effectText`	No	Full English effect description. Null when unavailable.
`damageClass`	No	Damage class: physical, special, or status. Null when unavailable.
`statChanges`	No	Stat stage changes caused by this move.
`effectChance`	No	Secondary effect chance percentage. Null when not applicable.
`shortEffectText`	No	Short English effect summary. Null when unavailable.
`learnedByPokemon`	No	Pokémon names that can learn this move (populated when include_learners=true).

Schema Changelog

Changes observed during successful MCP inspections.

Changed14 schema fields changedSep 19, 2026

removedOutput schema / properties / accuracy / anyOf

Removed value: -[
-  {
-    "type": "number"
-  },
-  {
-    "type": "null"
-  }
-]

addedOutput schema / properties / accuracy / type
```
Added value: +[
+  "number",
+  "null"
+]
```

removedOutput schema / properties / damageClass / anyOf

Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]

addedOutput schema / properties / damageClass / type
```
Added value: +[
+  "string",
+  "null"
+]
```

removedOutput schema / properties / effectChance / anyOf

Removed value: -[
-  {
-    "type": "number"
-  },
-  {
-    "type": "null"
-  }
-]

addedOutput schema / properties / effectChance / type
```
Added value: +[
+  "number",
+  "null"
+]
```

removedOutput schema / properties / effectText / anyOf

Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]

addedOutput schema / properties / effectText / type
```
Added value: +[
+  "string",
+  "null"
+]
```

removedOutput schema / properties / power / anyOf

Removed value: -[
-  {
-    "type": "number"
-  },
-  {
-    "type": "null"
-  }
-]

addedOutput schema / properties / power / type
```
Added value: +[
+  "number",
+  "null"
+]
```

removedOutput schema / properties / pp / anyOf

Removed value: -[
-  {
-    "type": "number"
-  },
-  {
-    "type": "null"
-  }
-]

addedOutput schema / properties / pp / type

Added value: +[
+  "number",
+  "null"
+]

removedOutput schema / properties / shortEffectText / anyOf

Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]

addedOutput schema / properties / shortEffectText / type
```
Added value: +[
+  "string",
+  "null"
+]
```

Changed6 schema fields changedAug 24, 2026

changedInput schema / $schema

Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"

addedInput schema / additionalProperties
```
Added value: +false
```

changedOutput schema / $schema

Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"

addedOutput schema / anyOf

Added value: +[
+  {
+    "not": {
+      "required": [
+        "error"
+      ]
+    },
+    "required": [
+      "id",
+      "name",
+      "type",
+      "damageClass",
+      "power",
+      "accuracy",
+      "pp",
+      "priority",
+      "effectChance",
+      "effectText",
+      "shortEffectText",
+      "target",
+      "statChanges",
+      "learnedByPokemon"
+    ]
+  },
+  {
+    "required": [
+      "error"
+    ]
+  }
+]

addedOutput schema / properties / error

Added value: +{
+  "additionalProperties": {},
+  "description": "Present when the call failed. Absent on success.",
+  "properties": {
+    "code": {
+      "description": "JSON-RPC error code for this failure.",
+      "maximum": 9007199254740991,
+      "minimum": -9007199254740991,
+      "type": "integer"
+    },
+    "data": {
+      "additionalProperties": {},
+      "properties": {
+        "reason": {
+          "description": "Machine-readable failure mode. Declared by this tool: `not_found`: The identifier resolves to no move in PokéAPI. Other values are possible when a failure originates below the handler.",
+          "examples": [
+            "not_found"
+          ],
+          "type": "string"
+        },
+        "recovery": {
+          "additionalProperties": {},
+          "description": "Actionable next step for the caller.",
+          "properties": {
+            "hint": {
+              "type": "string"
+            }
+          },
+          "required": [
+            "hint"
+          ],
+          "type": "object"
+        },
+        "retryable": {
+          "description": "Whether retrying may succeed.",
+          "type": "boolean"
+        }
+      },
+      "type": "object"
+    },
+    "message": {
+      "description": "Human-readable description of what went wrong.",
+      "type": "string"
+    }
+  },
+  "required": [
+    "code",
+    "message"
+  ],
+  "type": "object"
+}

removedOutput schema / required

Removed value: -[
-  "id",
-  "name",
-  "type",
-  "damageClass",
-  "power",
-  "accuracy",
-  "pp",
-  "priority",
-  "effectChance",
-  "effectText",
-  "shortEffectText",
-  "target",
-  "statChanges",
-  "learnedByPokemon"
-]

First observedJun 7, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already mark this as read-only, open-world, and idempotent, so the safety profile is covered. The description adds useful behavioral context by specifying that include_learners=true pulls the Pokémon learner list and that move names can be sourced from pokeapi_get_pokemon, while the schema notes the list can be large. No contradiction with annotations.

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 concise sentences: the first enumerates what is returned, the second explains the optional learner flag, and the third points to the sibling source for identifiers. Every sentence earns its place with 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?

With a rich output schema, read-only/idempotent annotations, and a fully documented two-parameter input schema, the description covers the key operational details: identifier format/source, optional learner list, and the move fields returned. Nothing needed for correct invocation 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 description coverage is 100%, so the schema already explains both identifier and include_learners. The description adds a useful cross-reference for obtaining move names and restates the learner flag, but it does not add significant parameter-level meaning beyond the schema.

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 opens with 'Get move details by name or numeric ID' and then enumerates the returned fields (type, damage class, power, accuracy, PP, priority, target, stat changes, status-effect chance, effect text). This is a specific verb+resource and clearly separates it from sibling tools like pokeapi_get_ability or pokeapi_get_item.

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?

The context is clear: this tool is for move details, and the description even points to pokeapi_get_pokemon as the source for valid move names when include_moves=true. It does not explicitly state when not to use this tool versus siblings, but the resource type (move) makes the appropriate use obvious.

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 tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.