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).
`learnersIncluded`	No	True when the learner list was requested, including when no learners are known.

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedSep 30, 2026

changedOutput schema / anyOf

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

addedOutput schema / properties / learnersIncluded

Added value: +{
+  "description": "True when the learner list was requested, including when no learners are known.",
+  "type": "boolean"
+}

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 declare readOnly, idempotent and open-world behavior, so the safety profile is covered. The description adds genuinely useful context beyond them: the warning that the learners list 'can be large' and a summary of exactly what fields come back. It does not mention rate limits, caching, or failure behavior for unknown identifiers.

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?

Two sentences, front-loaded with the action and payload, then the optional-parameter behavior and the cross-reference to where names come from. No filler or restated title.

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?

An output schema exists, so return values need no explanation, yet the description still orients the agent on payload scope. Identifier format, the optional flag's tradeoff, and the source of valid names are all covered for a simple two-parameter read tool.

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% and both parameters carry their own descriptions (identifier format, include_learners default and size caveat), so the schema does the heavy lifting. The description largely restates the include_learners semantics rather than adding format or edge-case detail beyond it.

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 specific verb and resource ('Get move details by name or numeric ID') and enumerates the payload categories (type, damage class, power, accuracy, PP, priority, target, stat changes, effect text), so it is unmistakably distinct from the ability/item/nature/pokemon siblings.

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?

Gives a clear conditional for the optional parameter ('Set include_learners=true to include the list of Pokémon that can learn the move') and routes the agent to pokeapi_get_pokemon with include_moves=true as the source of valid move names. It does not state when this tool should be preferred over other get_* tools, but for a lookup-by-name tool that guidance is largely implied.

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.