tibiawiki-mcp

tibia_search

Read-only

Find Tibia pages of any kind whose name contains a substring. Items also match by the name and plural the game prints. Turns an approximate or in-game name into the exact page name tibia_get expects. With a query, shortest name first, so the closest match leads. With types and no query, lists every page of those types by title, as in "list every mount".

Input Schema

TableJSON Schema

Name	Required	Description
`limit`	No
`query`	No	Substring to match against page names, case-insensitive. Omit it to list every page of types.
`types`	No	Restrict to these kinds of page. Defaults to all. Required without a query.
`cursor`	No	Opaque cursor from a previous call.
`include_inactive`	No	Include deprecated, event-only and unavailable pages.

Output Schema

TableJSON Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 25, 2026

changedInput schema / properties / types / description

Previous value: -"Restrict to these kinds of page. Defaults to all fourteen. Required without a query."New value: +"Restrict to these kinds of page. Defaults to all. Required without a query."

Changed3 schema fields changedSep 24, 2026

changedInput schema / properties / query / description

Previous value: -"Substring to match against page names, case-insensitive."New value: +"Substring to match against page names, case-insensitive. Omit it to list every page of types."

changedInput schema / properties / types / description

Previous value: -"Restrict to these kinds of page. Defaults to all fourteen."New value: +"Restrict to these kinds of page. Defaults to all fourteen. Required without a query."

removedInput schema / required
```
Removed value: -[
-  "query"
-]
```

First observedSep 15, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Beyond the readOnlyHint annotation, the description discloses meaningful behavior: substring matching, plural matching for items, shortest-name-first ordering, and list-all behavior when types are given without a query. This goes beyond a simple read-only declaration.

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 compact and front-loaded, with no filler. Each sentence earns its place: core behavior, item plural matching, tibia_get relationship, ordering rule, and list-mode example all contribute directly to correct tool use.

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?

Given the output schema, annotations, and 80% schema coverage, the description covers the main decision space well. It leaves minor gaps such as pagination/cursor guidance and explicit routing away from specialized finder siblings, but these are partially covered by the schema and sibling names.

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 80%, so the baseline is 3, but the description adds real semantic value: omitting query triggers type listing, and items match by game-printed plural as well as name. Limit, cursor, and include_inactive remain dependent on the schema, but the core query/types behavior is enriched.

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 opens with a specific verb and resource: 'Find Tibia pages of any kind whose name contains a substring.' It clearly distinguishes itself from type-specific siblings by emphasizing 'any kind' and by positioning itself as the resolver of approximate names before tibia_get.

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 explicit usage modes: query-based search for approximate names, and type-based listing when no query is provided. It does not explicitly name the specialized finder siblings as alternatives, but the phrase 'of any kind' and the tibia_get handoff make the intended context clear.

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.