tibiawiki-mcp

tibia_find_items

Read-only

Find Tibia items matching class, type and stat filters such as attack, defense, armor and required level, resistances, skill bonuses, imbuement slots, weight and hands. Use this for questions like "which two-handed swords need level 100 or less" or "which sorcerer items resist fire". Vocation and weapon type match by membership, so "knight" matches "knights". Call tibia_get on a title for the full item.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`sort`	No	weight ascends, armor, attack and defense descend, title is alphabetical. value descends by NPC gold price, and prices in other currencies come last.	title
`hands`	No
`leech`	No	Leeches everything listed.
`limit`	No
`cursor`	No
`vocation`	No	Matches required_vocation, e.g. "knight".
`armor_min`	No
`item_type`	No	e.g. "Sword Weapons".
`attack_max`	No
`attack_min`	No
`client_ids`	No	The item's client ID, any listed. Item variants can share one.
`item_class`	No	e.g. "Weapons", "Armors".
`weight_max`	No	In oz. Items without a weight never match.
`damage_type`	No	Weapon element.
`defense_min`	No
`skill_bonus`	No	Raises every listed skill.
`weapon_type`	No	e.g. "Sword", "Axe", "Club".
`is_stackable`	No
`resistant_to`	No	Resists everything listed (resistance above 0).
`is_pickupable`	No
`include_inactive`	No
`required_level_max`	No
`imbuement_slots_min`	No

Output Schema

TableJSON Schema

Name	Required	Description	Default
`results`	Yes
`nextCursor`	No
`totalMatches`	Yes
`indexGeneratedAt`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedSep 27, 2026

changedInput schema / properties / sort / description

Previous value: -"weight ascends, value, armor, attack and defense descend, title is alphabetical."New value: +"weight ascends, armor, attack and defense descend, title is alphabetical. value descends by NPC gold price, and prices in other currencies come last."

addedOutput schema / properties / results / items / properties / valueBuyCurrency

Added value: +{
+  "description": "Currency of the price beside it, as the wiki names it, e.g. Gold Coin, Tibia Coins or Event Points. null when there is no price.",
+  "type": [
+    "string",
+    "null"
+  ]
+}

changedOutput schema / properties / results / items / required

Previous value: -[
-  "title",
-  "actualName",
-  "itemClass",
-  "itemType",
-  "weight",
-  "valueBuy",
-  "clientId",
-  "isStackable",
-  "isPickupable",
-  "attributes"
-]New value: +[
+  "title",
+  "actualName",
+  "itemClass",
+  "itemType",
+  "weight",
+  "valueBuy",
+  "valueBuyCurrency",
+  "clientId",
+  "isStackable",
+  "isPickupable",
+  "attributes"
+]

Changed8 schema fields changedSep 25, 2026

addedInput schema / properties / damage_type

Added value: +{
+  "description": "Weapon element.",
+  "enum": [
+    "death",
+    "earth",
+    "energy",
+    "fire",
+    "holy",
+    "ice",
+    "physical"
+  ],
+  "type": "string"
+}

addedInput schema / properties / is_pickupable
```
Added value: +{
+  "type": "boolean"
+}
```
addedInput schema / properties / is_stackable
```
Added value: +{
+  "type": "boolean"
+}
```

addedInput schema / properties / leech

Added value: +{
+  "description": "Leeches everything listed.",
+  "items": {
+    "enum": [
+      "life",
+      "mana"
+    ],
+    "type": "string"
+  },
+  "type": "array"
+}

addedOutput schema / properties / results / items / properties / actualName

Added value: +{
+  "description": "Name as the game prints it.",
+  "type": [
+    "string",
+    "null"
+  ]
+}

addedOutput schema / properties / results / items / properties / isPickupable
```
Added value: +{
+  "type": [
+    "boolean",
+    "null"
+  ]
+}
```
addedOutput schema / properties / results / items / properties / isStackable
```
Added value: +{
+  "type": [
+    "boolean",
+    "null"
+  ]
+}
```

changedOutput schema / properties / results / items / required

Previous value: -[
-  "title",
-  "itemClass",
-  "itemType",
-  "weight",
-  "valueBuy",
-  "clientId",
-  "attributes"
-]New value: +[
+  "title",
+  "actualName",
+  "itemClass",
+  "itemType",
+  "weight",
+  "valueBuy",
+  "clientId",
+  "isStackable",
+  "isPickupable",
+  "attributes"
+]

Changed3 schema fields changedSep 24, 2026

addedInput schema / properties / client_ids

Added value: +{
+  "description": "The item's client ID, any listed. Item variants can share one.",
+  "items": {
+    "exclusiveMinimum": 0,
+    "maximum": 9007199254740991,
+    "type": "integer"
+  },
+  "maxItems": 100,
+  "minItems": 1,
+  "type": "array"
+}

addedOutput schema / properties / results / items / properties / clientId
```
Added value: +{
+  "type": [
+    "number",
+    "null"
+  ]
+}
```

changedOutput schema / properties / results / items / required

Previous value: -[
-  "title",
-  "itemClass",
-  "itemType",
-  "weight",
-  "valueBuy",
-  "attributes"
-]New value: +[
+  "title",
+  "itemClass",
+  "itemType",
+  "weight",
+  "valueBuy",
+  "clientId",
+  "attributes"
+]

Changed2 schema fields changedSep 24, 2026

changedInput schema / properties / resistant_to / description

Previous value: -"Resists every listed element (resistance above 0)."New value: +"Resists everything listed (resistance above 0)."

changedInput schema / properties / resistant_to / items / enum

Previous value: -[
-  "physical",
-  "earth",
-  "fire",
-  "ice",
-  "energy",
-  "death",
-  "holy",
-  "drown",
-  "lifedrain"
-]New value: +[
+  "physical",
+  "earth",
+  "fire",
+  "ice",
+  "energy",
+  "death",
+  "holy",
+  "drown",
+  "lifedrain",
+  "manadrain",
+  "critical_hit"
+]

Changed7 schema fields changedSep 24, 2026

addedInput schema / properties / hands

Added value: +{
+  "enum": [
+    "one",
+    "two"
+  ],
+  "type": "string"
+}

addedInput schema / properties / imbuement_slots_min

Added value: +{
+  "maximum": 9007199254740991,
+  "minimum": -9007199254740991,
+  "type": "integer"
+}

addedInput schema / properties / resistant_to

Added value: +{
+  "description": "Resists every listed element (resistance above 0).",
+  "items": {
+    "enum": [
+      "physical",
+      "earth",
+      "fire",
+      "ice",
+      "energy",
+      "death",
+      "holy",
+      "drown",
+      "lifedrain"
+    ],
+    "type": "string"
+  },
+  "type": "array"
+}

addedInput schema / properties / skill_bonus

Added value: +{
+  "description": "Raises every listed skill.",
+  "items": {
+    "enum": [
+      "magic_level",
+      "sword",
+      "axe",
+      "club",
+      "distance",
+      "fist",
+      "shielding"
+    ],
+    "type": "string"
+  },
+  "type": "array"
+}

addedInput schema / properties / sort / description

Added value: +"weight ascends, value, armor, attack and defense descend, title is alphabetical."

changedInput schema / properties / sort / enum

Previous value: -[
-  "title",
-  "weight",
-  "value"
-]New value: +[
+  "title",
+  "weight",
+  "value",
+  "armor",
+  "attack",
+  "defense"
+]

addedInput schema / properties / weight_max

Added value: +{
+  "description": "In oz. Items without a weight never match.",
+  "type": "number"
+}

First observedSep 15, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already declare the safe read profile (readOnlyHint=true, openWorldHint=false), so the description is free to add semantics it alone can supply: membership-style matching for vocation/weapon type ('knight' matches 'knights') and the fact that results are summaries requiring tibia_get for full data. It omits pagination/limit behavior on a 23-parameter search, which is the notable remaining gap.

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 sentences, front-loaded with the capability, then two illustrative queries, then the matching quirk and the follow-up call. Every sentence carries distinct information; nothing is padding.

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?

An output schema exists, so return values need no explanation, and the description covers the dominant filter use cases plus the tibia_get follow-up. For a 23-parameter tool with 0 required params, the missing notes on pagination and sort defaults are a modest but real incompleteness.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is only 48%, so the description must compensate, and it largely does: it names the filter families an agent is likely to reach for and adds non-obvious matching semantics for vocation and weapon_type that the schema does not state. Sort, limit/cursor, client_ids, include_inactive, is_stackable and is_pickupable remain undocumented in both places.

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 ('Find Tibia items') and enumerates the filter dimensions covered (class, type, attack, defense, armor, level, resistances, skill bonuses, imbuement slots, weight, hands). The resource noun cleanly separates it from tibia_find_creatures, tibia_find_spells, tibia_find_houses and the other find_* 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?

Provides concrete triggering questions ('which two-handed swords need level 100 or less', 'which sorcerer items resist fire') and routes the agent onward to tibia_get for full item detail. It never states when *not* to use it or what the alternative would be for a different query shape, but the context is clear.

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

All tibiawiki-mcp 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.

tibia_find_items

Input Schema

Output Schema

Schema Changelog

TDQS

Glama MCP Gateway

Resources