tibiawiki-mcp

by tibia-sh

Overview Schema Source Related Servers Discussions Admin

TypeScript

Local

tibia_where_to_sell

Read-only

Find the NPC paying the most gold for each item, grouped by city and NPC. Get gold prices for your items.

Instructions

Answers "where do I sell all this": for each item, the active NPC paying the most, grouped by city and NPC. Prices are NPC prices in gold. Call tibia_get on an NPC for more.

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": {
      "items": "<items>"
    },
    "name": "tibia_where_to_sell"
  }
}

Input Schema

Name	Required	Description	Default
`items`	Yes	Item names, any case, as the wiki titles them or the game prints them, e.g. "Dragon Shield" or "vial of lifefluid".

Output Schema

Name	Required	Description
`cities`	Yes
`noGoldBuyer`	Yes	Items no active NPC buys for gold.
`unknownItems`	Yes	Names that match no item.
`ambiguousItems`	Yes	Names more than one item goes by, with those items.
`indexGeneratedAt`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed7 schema fields changedv0.13.0Sep 26, 2026

changedInput schema / properties / items / description

Previous value: -"Exact item names, any case, e.g. \"Dragon Shield\"."New value: +"Item names, any case, as the wiki titles them or the game prints them, e.g. \"Dragon Shield\" or \"vial of lifefluid\"."

addedOutput schema / properties / ambiguousItems

Added value: +{
+  "description": "Names more than one item goes by, with those items.",
+  "items": {
+    "additionalProperties": false,
+    "properties": {
+      "candidates": {
+        "items": {
+          "type": "string"
+        },
+        "type": "array"
+      },
+      "input": {
+        "type": "string"
+      }
+    },
+    "required": [
+      "input",
+      "candidates"
+    ],
+    "type": "object"
+  },
+  "type": "array"
+}

addedOutput schema / properties / cities / items / properties / buyers / items / properties / items / items / properties / input
```
Added value: +{
+  "description": "The name as you first wrote it.",
+  "type": "string"
+}
```
changedOutput schema / properties / cities / items / properties / buyers / items / properties / items / items / required
```
Previous value: -[
-  "item",
-  "price"
-]New value: +[
+  "item",
+  "input",
+  "price"
+]
```

addedOutput schema / properties / cities / items / properties / buyers / items / properties / position / description

Added value: +"For Rashid, who moves city daily, a buyer's city and position coordinates are null. His NPC page and tibia_where_to_sell give his week as rashidSchedule."

changedOutput schema / properties / cities / items / properties / city / description

Previous value: -"null for Rashid, who moves daily: see rashidSchedule."New value: +"For Rashid, who moves city daily, a buyer's city and position coordinates are null. His NPC page and tibia_where_to_sell give his week as rashidSchedule."

changedOutput schema / required

Previous value: -[
-  "cities",
-  "noGoldBuyer",
-  "unknownItems",
-  "indexGeneratedAt"
-]New value: +[
+  "cities",
+  "noGoldBuyer",
+  "unknownItems",
+  "ambiguousItems",
+  "indexGeneratedAt"
+]

Addedv0.10.0Sep 25, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already mark this as read-only, so the description does not need to restate safety. It adds meaningful behavior: results are the active NPC paying the most, grouped by city and NPC, and prices are NPC prices in gold. This fills in the semantics of 'where to sell' beyond what the annotations provide.

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?

Two sentences deliver the core behavior, output grouping, price units, and a follow-up routing hint without any filler. The user-facing question is front-loaded, making the tool's purpose immediately recognizable.

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 tool with an output schema present, the description is complete: it states what input is processed, how results are grouped, what the prices mean, and where to go for further detail. Nothing essential is missing for an agent to invoke 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 schema already documents the items parameter including case-insensitivity and format examples. The description adds only the minor context that each item is processed individually, which does not substantially extend the schema's guidance.

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?

The description names a specific verb-resource pair: it answers where to sell items by finding the active NPC paying the most per item. It clearly distinguishes itself from siblings like tibia_how_to_obtain by focusing on selling rather than obtaining, and from tibia_get by positioning itself as the aggregation tool with tibia_get as the follow-up.

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?

The opening phrase "Answers 'where do I sell all this'" gives clear context for when the tool is appropriate. It does not explicitly list exclusions or compare with alternatives, but it does point to tibia_get for more detail on an NPC, which guides the agent to the natural next step rather than leaving it to guess.

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

Deploy Server