tibiawiki-mcp

Overview Schema Source Related Servers Discussions Admin

tibia_find_items

Read-only

Search Tibia items by class, type, required level, stats, resistances, skills, imbuement slots, weight, or hands to find gear matching specific criteria.

Instructions

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.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "tibia_find_items"
  }
}

Input 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	Matches any of an item's client IDs. 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

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

Schema Changelog

Changes observed during successful MCP inspections.

Changed5 schema fields changedv0.22.0Nov 5, 2026

changedInput schema / properties / client_ids / description

Previous value: -"The item's client ID, any listed. Item variants can share one."New value: +"Matches any of an item's client IDs. Item variants can share one."

addedOutput schema / properties / results / items / properties / articleId
```
Added value: +{
+  "type": "number"
+}
```

addedOutput schema / properties / results / items / properties / clientIds

Added value: +{
+  "items": {
+    "type": "number"
+  },
+  "type": "array"
+}

addedOutput schema / properties / results / items / properties / valueBuy / description
```
Added value: +"Price an NPC sells it for, in valueBuyCurrency. 0: no NPC sells it."
```

changedOutput schema / properties / results / items / required

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

Changed3 schema fields changedv0.17.1Oct 1, 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 changedv0.13.0Sep 26, 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"
+]

Changed10 schema fields changedv0.10.0Sep 25, 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"
+}

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 everything listed (resistance above 0).",
+  "items": {
+    "enum": [
+      "physical",
+      "earth",
+      "fire",
+      "ice",
+      "energy",
+      "death",
+      "holy",
+      "drown",
+      "lifedrain",
+      "manadrain",
+      "critical_hit"
+    ],
+    "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"
+}

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"
+]

Changed15 schema fields changedv0.5.0Sep 15, 2026

removedInput schema / additionalProperties
```
Removed value: -{}
```

addedInput schema / properties / armor_min

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

addedInput schema / properties / attack_max

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

addedInput schema / properties / attack_min

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

addedInput schema / properties / cursor
```
Added value: +{
+  "type": "string"
+}
```

addedInput schema / properties / defense_min

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

addedInput schema / properties / include_inactive

Added value: +{
+  "default": false,
+  "type": "boolean"
+}

addedInput schema / properties / item_class

Added value: +{
+  "description": "e.g. \"Weapons\", \"Armors\".",
+  "type": "string"
+}

addedInput schema / properties / item_type

Added value: +{
+  "description": "e.g. \"Sword Weapons\".",
+  "type": "string"
+}

addedInput schema / properties / limit

Added value: +{
+  "default": 25,
+  "maximum": 100,
+  "minimum": 1,
+  "type": "integer"
+}

addedInput schema / properties / required_level_max

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

addedInput schema / properties / sort

Added value: +{
+  "default": "title",
+  "enum": [
+    "title",
+    "weight",
+    "value"
+  ],
+  "type": "string"
+}

addedInput schema / properties / vocation

Added value: +{
+  "description": "Matches required_vocation, e.g. \"knight\".",
+  "type": "string"
+}

addedInput schema / properties / weapon_type

Added value: +{
+  "description": "e.g. \"Sword\", \"Axe\", \"Club\".",
+  "type": "string"
+}

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "https://json-schema.org/draft/2020-12/schema",
+  "additionalProperties": false,
+  "properties": {
+    "indexGeneratedAt": {
+      "type": "string"
+    },
+    "nextCursor": {
+      "type": "string"
+    },
+    "results": {
+      "items": {
+        "additionalProperties": false,
+        "properties": {
+          "attributes": {
+            "additionalProperties": {
+              "type": [
+                "string",
+                "number"
+              ]
+            },
+            "propertyNames": {
+              "type": "string"
+            },
+            "type": "object"
+          },
+          "itemClass": {
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "itemType": {
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "title": {
+            "type": "string"
+          },
+          "valueBuy": {
+            "type": [
+              "number",
+              "null"
+            ]
+          },
+          "weight": {
+            "type": [
+              "number",
+              "null"
+            ]
+          }
+        },
+        "required": [
+          "title",
+          "itemClass",
+          "itemType",
+          "weight",
+          "valueBuy",
+          "attributes"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "totalMatches": {
+      "type": "number"
+    }
+  },
+  "required": [
+    "results",
+    "totalMatches",
+    "indexGeneratedAt"
+  ],
+  "type": "object"
+}

First observedv0.1.0Sep 12, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered; the description adds genuinely non-obvious behavior — that vocation and weapon_type match by membership ("knight" matches "knights"). It does not disclose result ordering defaults or pagination behavior, which matters for a 23-filter search.

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?

Three tight sentences with the core capability front-loaded, followed by usage examples and a hand-off to tibia_get. The examples earn their space; nothing is padded, though the filter enumeration is a long list that could be trimmed.

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?

Output schema exists, so return values need no explanation, and annotations cover the read-only profile. For a 23-parameter tool the description gives an agent enough to construct a reasonable query, but it omits how to paginate or what happens when no filters are supplied (the default unbounded list).

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?

With only 48% schema description coverage across 23 parameters, the description has to compensate. It usefully names several otherwise-undocumented filters (hands, weight, required level, imbuement slots, resistances, skill bonuses) and explains membership matching, but leaves the _min/_max numeric pairs, is_stackable, is_pickupable, include_inactive, limit and cursor unexplained 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?

Opens with a specific verb+resource ("Find Tibia items") and enumerates the actual filterable dimensions (class, type, attack/defense/armor, level, resistances, skill bonuses, imbuements, weight, hands). This distinguishes it cleanly from the sibling finders (creatures, houses, quests, spells) which target entirely different entities.

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 two concrete natural-language query examples ("which two-handed swords need level 100 or less", "which sorcerer items resist fire") and explicitly routes to tibia_get for full item detail. It stops short of stating when to prefer tibia_search or tibia_how_to_obtain over this tool, so the alternative-selection guidance is incomplete.

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

Deploy Server

tibia_find_items

Instructions

Tool call template

Input Schema

Output Schema

Schema Changelog

TDQS

Other Tools