tibiawiki-mcp

Overview Schema Source Related Servers Discussions Admin

tibia_find_travel

Read-only

Look up boat, carpet, and other travel routes to or from a place with fares and NPC details. Returns individual legs; it does not plan journeys.

Instructions

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.

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_travel"
  }
}

Input 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

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

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedv0.22.0Nov 5, 2026

addedOutput schema / properties / results / items / properties / articleId
```
Added value: +{
+  "description": "The NPC's.",
+  "type": "number"
+}
```

changedOutput schema / properties / results / items / required

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

Addedv0.13.0Sep 26, 2026

TDQS

A4/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety profile is covered. The description adds genuine context beyond that: each row is one leg, carries origin plus the NPC's recorded city/location/position, and fares are included. It does not discuss pagination behavior of cursor/limit, but that is partly structural.

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 short sentences, front-loaded with the capability and then the row-granularity clarification. Every sentence earns its place; no filler.

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-value explanation is not required. For a six-optional-param, read-only, closed-world finder, the description covers the resource, row granularity, and the non-planning limitation. The main remaining gaps are cursor/limit/include_inactive guidance, which is minor for this tool archetype.

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 coverage is only 50%, so one would hope for compensation. The description's 'to or from a place' maps to the to/from params and 'with fares' hints at price sorting, but sort, limit, cursor and include_inactive receive no explanation in the description and remain undocumented or thinly documented in the schema. Baseline 3 is appropriate given the mixed coverage.

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 boat/carpet/other travel routes to or from a place, with fares. The travel-route resource is clearly distinct from the sibling families (creatures, houses, items, quests, spells), so an agent can route without opening the schema.

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 a clear exclusion — 'Rows are single legs: this does not plan journeys' — which tells the agent not to reach for this for multi-hop trip planning. It stops short of naming an alternative tool or spelling out when a place name should be used versus a broader search.

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

Deploy Server