tibiawiki-mcp

tibia_find_travel

Read-only

Find boat, carpet and other travel routes to or from a place, with fares. Each row is one leg with its start (origin) and the NPC's recorded city, location and position. Rows are single legs: this does not plan journeys.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`to`	No	Exact destination, e.g. "Svargrond", any case.
`from`	No	Exact start place of the leg, e.g. "Meriana", any case.
`sort`	No	price ascends with 0 fares last, npc is alphabetical.	price
`limit`	No
`cursor`	No
`include_inactive`	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.

Changed5 schema fields changedSep 26, 2026

addedInput schema / additionalProperties
```
Added value: +false
```

addedInput schema / properties / from

Added value: +{
+  "description": "Exact start place of the leg, e.g. \"Meriana\", any case.",
+  "minLength": 1,
+  "type": "string"
+}

removedInput schema / properties / from_city

Removed value: -{
-  "description": "Exact city of the NPC, any case.",
-  "minLength": 1,
-  "type": "string"
-}

addedOutput schema / properties / results / items / properties / origin

Added value: +{
+  "description": "Where the leg starts. null: not recorded, it starts at one of the NPC's positions.",
+  "type": [
+    "string",
+    "null"
+  ]
+}

changedOutput schema / properties / results / items / required

Previous value: -[
-  "npc",
-  "city",
-  "subarea",
-  "location",
-  "position",
-  "to",
-  "price",
-  "notes"
-]New value: +[
+  "npc",
+  "city",
+  "subarea",
+  "location",
+  "position",
+  "to",
+  "origin",
+  "price",
+  "notes"
+]

AddedSep 25, 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, so the agent knows this is a safe read operation. The description adds valuable behavioral context beyond the annotations: rows represent single legs, each row includes the start/origin and the NPC's recorded city, location, and position, and fares are included. This helps the agent interpret results correctly.

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?

The description is three sentences with no filler. It front-loads the core action and resource, then adds the key row-level detail and the important limitation. Every sentence earns its place.

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?

The description covers the essential semantics for a read-only lookup tool, and the output schema handles return-value details. It clearly states the single-leg limitation and row composition. It could be slightly more complete by mentioning pagination or the inactive-route filter, but these are secondary given the schema defaults and output schema.

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

Parameters2/5

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

Schema description coverage is 50%, with limit, cursor, and include_inactive left undocumented in the schema. The description does not compensate for these gaps; it only restates the general to/from concept already covered by the schema. It adds no meaning for the pagination, limit, or inactive-route parameters.

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 uses a specific verb ('Find') and resource ('boat, carpet and other travel routes') and clearly distinguishes this tool from the sibling find_* tools by focusing on travel. It also clarifies the output granularity ('Each row is one leg') and what the tool does not do ('does not plan journeys'), leaving no ambiguity about its purpose.

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 description gives clear context on when to use the tool: to look up individual travel legs with fares. It explicitly states a when-not ('does not plan journeys'), which prevents misuse for multi-leg trip planning, though it does not name a specific alternative tool for journey planning.

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.