tibiawiki-mcp

Overview Schema Source Related Servers Discussions Admin

tibia_how_to_obtain

Read-only

Find every in-game source for an item: creature drop chances, NPC vendors and prices, and quest rewards in one lookup, with paginated droppers.

Instructions

Every in-game source for one item: which creatures drop it and how likely, which NPCs sell it and for how much (the price the player pays), and which quests reward it. Droppers come up to 100 at a time, with a cursor for the rest. Vendors and quest rewards always come whole. Prefer this over three separate lookups.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "item_name": "<item_name>"
    },
    "name": "tibia_how_to_obtain"
  }
}

Input Schema

Name	Required	Description
`limit`	No	Pages droppedBy only. NPCs and quests come whole on every page.
`cursor`	No
`item_name`	Yes	Item page name or the name the game prints, e.g. "Dragon Shield".
`include_inactive`	No	Include deprecated or event-only creatures, NPCs and quests as sources.

Output Schema

Name	Required	Description
`item`	Yes
`note`	Yes
`source`	Yes
`status`	Yes
`clientId`	Yes	The first client ID.
`articleId`	Yes
`clientIds`	Yes
`droppedBy`	Yes
`nextCursor`	No
`soldByNpcs`	Yes
`questRewards`	Yes
`droppedByTotal`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed12 schema fields changedv0.22.0Nov 5, 2026

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

addedInput schema / properties / limit

Added value: +{
+  "default": 100,
+  "description": "Pages droppedBy only. NPCs and quests come whole on every page.",
+  "maximum": 100,
+  "minimum": 1,
+  "type": "integer"
+}

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

addedOutput schema / properties / clientId

Added value: +{
+  "description": "The first client ID.",
+  "type": [
+    "number",
+    "null"
+  ]
+}

addedOutput schema / properties / clientIds

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

addedOutput schema / properties / droppedBy / items / properties / articleId
```
Added value: +{
+  "type": "number"
+}
```
addedOutput schema / properties / droppedBy / items / properties / chance / description
```
Added value: +"Drop chance in percent."
```

addedOutput schema / properties / droppedBy / items / properties / min / description

Added value: +"Start of the wiki's amount range. 0 when the wiki gives one amount, which max holds, or a range from 0."

changedOutput schema / properties / droppedBy / items / required

Previous value: -[
-  "creature",
-  "chance",
-  "min",
-  "max"
-]New value: +[
+  "creature",
+  "articleId",
+  "chance",
+  "min",
+  "max"
+]

addedOutput schema / properties / droppedByTotal
```
Added value: +{
+  "type": "number"
+}
```
addedOutput schema / properties / nextCursor
```
Added value: +{
+  "type": "string"
+}
```

changedOutput schema / required

Previous value: -[
-  "item",
-  "status",
-  "droppedBy",
-  "soldByNpcs",
-  "questRewards",
-  "note",
-  "source"
-]New value: +[
+  "item",
+  "articleId",
+  "clientId",
+  "clientIds",
+  "status",
+  "droppedBy",
+  "droppedByTotal",
+  "soldByNpcs",
+  "questRewards",
+  "note",
+  "source"
+]

Changed1 schema field changedv0.13.0Sep 26, 2026

changedInput schema / properties / item_name / description

Previous value: -"Item page name, e.g. \"Dragon Shield\"."New value: +"Item page name or the name the game prints, e.g. \"Dragon Shield\"."

Changed5 schema fields changedv0.5.0Sep 15, 2026

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

addedInput schema / properties / include_inactive

Added value: +{
+  "default": false,
+  "description": "Include deprecated or event-only creatures, NPCs and quests as sources.",
+  "type": "boolean"
+}

addedInput schema / properties / item_name

Added value: +{
+  "description": "Item page name, e.g. \"Dragon Shield\".",
+  "minLength": 1,
+  "type": "string"
+}

addedInput schema / required
```
Added value: +[
+  "item_name"
+]
```

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "https://json-schema.org/draft/2020-12/schema",
+  "additionalProperties": false,
+  "properties": {
+    "droppedBy": {
+      "items": {
+        "additionalProperties": false,
+        "properties": {
+          "chance": {
+            "type": [
+              "number",
+              "null"
+            ]
+          },
+          "creature": {
+            "type": "string"
+          },
+          "max": {
+            "type": [
+              "number",
+              "null"
+            ]
+          },
+          "min": {
+            "type": [
+              "number",
+              "null"
+            ]
+          }
+        },
+        "required": [
+          "creature",
+          "chance",
+          "min",
+          "max"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "item": {
+      "type": "string"
+    },
+    "note": {
+      "type": "string"
+    },
+    "questRewards": {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "soldByNpcs": {
+      "items": {
+        "additionalProperties": false,
+        "properties": {
+          "city": {
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "currency": {
+            "type": "string"
+          },
+          "npc": {
+            "type": "string"
+          },
+          "price": {
+            "type": "number"
+          }
+        },
+        "required": [
+          "npc",
+          "city",
+          "price",
+          "currency"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "source": {
+      "additionalProperties": false,
+      "properties": {
+        "indexGeneratedAt": {
+          "type": "string"
+        },
+        "page": {
+          "type": "string"
+        },
+        "url": {
+          "type": "string"
+        }
+      },
+      "required": [
+        "page",
+        "url",
+        "indexGeneratedAt"
+      ],
+      "type": "object"
+    },
+    "status": {
+      "type": [
+        "string",
+        "null"
+      ]
+    }
+  },
+  "required": [
+    "item",
+    "status",
+    "droppedBy",
+    "soldByNpcs",
+    "questRewards",
+    "note",
+    "source"
+  ],
+  "type": "object"
+}

First observedv0.1.0Sep 12, 2026

TDQS

A4.4/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 contributes genuine extra context about result completeness (droppers capped at 100 with cursor, vendors and quests always returned whole). It stops short of describing not-found behavior or error cases, which would be the remaining behavioral 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 core purpose, then pagination semantics, then the routing hint. No sentence is redundant and the ordering matches how an agent would reason about calling it.

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?

With an output schema present, return-value shape need not be spelled out, and annotations cover the safety profile; the description adds the pagination and completeness rules an agent needs. Only the include_inactive switch is unaddressed in prose, a minor omission given its schema description exists.

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 75%, so the schema carries most of the load, and the description reinforces it by explaining that only droppers paginate ('Droppers come up to 100 at a time, with a cursor for the rest; Vendors and quest rewards always come whole'). This actively clarifies the limit/cursor interaction beyond the raw schema, though include_inactive is left to 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?

States a specific verb+resource ('Every in-game source for one item') and enumerates the three result classes: creature drops with probabilities, NPC vendors with prices, and quest rewards. This is distinctly different from siblings like tibia_where_to_sell, which answers the inverse question.

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?

'Prefer this over three separate lookups' tells the agent when to reach for this tool rather than composing multiple calls, giving clear usage context. However, it never names the actual sibling tools (e.g. tibia_find_items, tibia_where_to_sell) it supersedes, so the routing signal is implicit rather than explicit.

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

Deploy Server