pokeapi-mcp-server

Get Item

pokeapi_get_item

Read-onlyIdempotent

Get item details by name or numeric ID — effect text, category, in-game cost, 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	Purchase cost in Pokédollars. 0 means not sold in shops.
`name`	No	Item name in hyphenated lowercase.
`error`	No	Present when the call failed. Absent on success.
`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.

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.8/5.0

Behavior3/5

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

Annotations already declare readOnlyHint, openWorldHint, and idempotentHint, covering the safety profile. The description adds value by enumerating the expected response fields, but it does not disclose behaviors like error handling, rate limits, or response structure beyond what the output schema already provides.

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?

A single, front-loaded sentence that states the verb, resource, lookup method, and a detailed but compact enumeration of return values. Every phrase earns its place; no filler or redundancy.

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

Completeness4/5

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

For a simple read-only lookup tool with one parameter, a thorough schema, and an output schema, the description is nearly complete. The only missing context is error/not-found behavior (e.g., what happens for an invalid identifier), which is a minor gap for this tool's simplicity.

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 the identifier parameter is already well-documented with format examples ('choice-specs', 'leftovers') and type constraints (lowercase hyphenated name or numeric ID as string). The description merely restates 'by name or numeric ID' without adding further semantic 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?

Description begins with a specific verb-resource pair ('Get item details') and elaborates with a concrete list of returned fields (effect text, category, cost, etc.). The item domain clearly distinguishes it from sibling tools focused on Pokémon, abilities, moves, natures, and type matchups.

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

Usage Guidelines3/5

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

The description makes the use case implicit ('Get item details by name or numeric ID') but never explicitly states when to use this tool over alternatives or when not to use it. There is no mention of sibling tools or exclusion criteria, leaving the agent to infer from the domain.

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.