pokeapi-mcp-server

Get Item

pokeapi_get_item

Read-onlyIdempotent

Get item details by name or numeric ID — effect text, category, versioned purchase and sell prices, fling power, item attributes (holdable, consumable, etc.), sprite URL, and Pokémon that commonly hold it.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`identifier`	Yes	Item name in lowercase hyphenated form (e.g. "choice-specs", "leftovers") or numeric ID as a string.

Output Schema

TableJSON Schema

Name	Required	Description
`id`	No	Item ID.
`cost`	No	Legacy Pokédollar cost when supplied. Null when unavailable; zero is a literal amount. Independent of versioned prices.
`name`	No	Item name in hyphenated lowercase.
`error`	No	Present when the call failed. Absent on success.
`prices`	No	All supplied price records in upstream order. Empty when no records are available.
`category`	No	Item category (e.g. "held-items", "medicine").
`spriteUrl`	No	Item sprite URL. Null when no sprite is available.
`attributes`	No	Item attributes (e.g. "holdable", "consumable", "usable-in-battle").
`effectText`	No	Full English effect description. Null when unavailable.
`flingPower`	No	Fling move base power when this item is flung. Null if not throwable.
`heldByPokemon`	No	Pokémon that commonly hold this item in the wild.
`shortEffectText`	No	Short English effect summary. Null when unavailable.

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedSep 30, 2026

changedOutput schema / anyOf

Previous value: -[
-  {
-    "not": {
-      "required": [
-        "error"
-      ]
-    },
-    "required": [
-      "id",
-      "name",
-      "category",
-      "cost",
-      "flingPower",
-      "effectText",
-      "shortEffectText",
-      "attributes",
-      "heldByPokemon",
-      "spriteUrl"
-    ]
-  },
-  {
-    "required": [
-      "error"
-    ]
-  }
-]New value: +[
+  {
+    "not": {
+      "required": [
+        "error"
+      ]
+    },
+    "required": [
+      "id",
+      "name",
+      "category",
+      "cost",
+      "prices",
+      "flingPower",
+      "effectText",
+      "shortEffectText",
+      "attributes",
+      "heldByPokemon",
+      "spriteUrl"
+    ]
+  },
+  {
+    "required": [
+      "error"
+    ]
+  }
+]

changedOutput schema / properties / cost / description

Previous value: -"Purchase cost in Pokédollars. 0 means not sold in shops."New value: +"Legacy Pokédollar cost when supplied. Null when unavailable; zero is a literal amount. Independent of versioned prices."

changedOutput schema / properties / cost / type

Previous value: -"number"New value: +[
+  "number",
+  "null"
+]

addedOutput schema / properties / prices

Added value: +{
+  "description": "All supplied price records in upstream order. Empty when no records are available.",
+  "items": {
+    "additionalProperties": false,
+    "description": "One version and currency price record.",
+    "properties": {
+      "currency": {
+        "description": "Currency name for both prices.",
+        "type": "string"
+      },
+      "purchasePrice": {
+        "description": "Purchase price in this currency and version group. Null means not purchasable; zero is a literal amount.",
+        "type": [
+          "number",
+          "null"
+        ]
+      },
+      "sellPrice": {
+        "description": "Sell price in this currency and version group. Null means not sellable; zero is a literal amount.",
+        "type": [
+          "number",
+          "null"
+        ]
+      },
+      "versionGroup": {
+        "description": "Version group these prices apply to.",
+        "type": "string"
+      }
+    },
+    "required": [
+      "versionGroup",
+      "currency",
+      "purchasePrice",
+      "sellPrice"
+    ],
+    "type": "object"
+  },
+  "type": "array"
+}

Changed8 schema fields changedSep 19, 2026

removedOutput schema / properties / effectText / anyOf

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

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

removedOutput schema / properties / flingPower / anyOf

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

addedOutput schema / properties / flingPower / 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"
+]
```

removedOutput schema / properties / spriteUrl / anyOf

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

addedOutput schema / properties / spriteUrl / 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",
+      "category",
+      "cost",
+      "flingPower",
+      "effectText",
+      "shortEffectText",
+      "attributes",
+      "heldByPokemon",
+      "spriteUrl"
+    ]
+  },
+  {
+    "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 item 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",
-  "category",
-  "cost",
-  "flingPower",
-  "effectText",
-  "shortEffectText",
-  "attributes",
-  "heldByPokemon",
-  "spriteUrl"
-]

First observedJun 7, 2026

TDQS

A3.6/5.0

Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint and openWorldHint, so the safety profile is covered. The description adds a field inventory (prices, fling power, holdable/consumable attributes, sprite URL, common holders), but that is return content already conveyed by the output schema, and no behavioral traits (caching, rate limits, missing-item behavior) are disclosed.

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?

One sentence, front-loaded with verb and resource, with zero preamble or filler. The trailing field enumeration is somewhat redundant against the output schema, which slightly dilutes the otherwise tight structure.

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 read-only lookup, everything needed to invoke correctly is present: the key format is in the schema, safety semantics are in annotations, and return shape is covered by the output schema. No critical gap remains for an agent 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%, so the single identifier parameter is fully documented in the schema, including the lowercase-hyphenated format and numeric-ID-as-string convention. The description's 'by name or numeric ID' restates the schema rather than adding syntax or edge-case detail.

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 (get) and resource (item details) and makes the lookup key explicit (name or numeric ID). The resource noun alone cleanly separates it from the sibling set (pokemon, ability, move, nature, type matchups), none of which overlap with items.

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

Usage Guidelines2/5

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

The description never says when to reach for this tool, when not to, or what alternative exists if the agent has something other than an item name/ID. Usage is only inferable from the tool name itself, and no prerequisites or exclusions are given.

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.