tibiawiki-mcp

Overview Schema Source Related Servers Discussions Admin

tibia_find_houses

Read-only

Search Tibia houses and guildhalls by city, rent, beds, size, or guildhall status, then sort results to find matches like the cheapest two-bed house in Thais.

Instructions

Find Tibia houses and guildhalls by city, rent, beds and size. Use this for questions like "cheapest house in Thais with two beds". Call tibia_get with a title for its location and position.

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

Input Schema

Name	Required	Description	Default
`city`	No	Exact city name, e.g. "Thais", any case.
`sort`	No	rent ascends, size descends, title is alphabetical.	rent
`limit`	No
`cursor`	No
`beds_min`	No
`rent_max`	No	Highest monthly rent in gold.
`size_min`	No	Fewest tiles.
`is_guildhall`	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: +{
+  "type": "number"
+}
```

changedOutput schema / properties / results / items / required

Previous value: -[
-  "title",
-  "city",
-  "street",
-  "rent",
-  "beds",
-  "size",
-  "rooms",
-  "floors",
-  "isGuildhall"
-]New value: +[
+  "title",
+  "articleId",
+  "city",
+  "street",
+  "rent",
+  "beds",
+  "size",
+  "rooms",
+  "floors",
+  "isGuildhall"
+]

Addedv0.10.0Sep 25, 2026

TDQS

A3.7/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 the tibia_get follow-up flow, but says nothing about pagination behavior (cursor/limit), what include_inactive does, or the default sort ordering beyond what the schema already documents.

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, front-loaded with the resource and filters, then the concrete example and cross-tool pointer. No wasted text.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With 9 optional params, pagination via cursor, and an include_inactive flag, the description should say more about result-set behavior and default sorting. The output schema relieves it of explaining return values, which keeps this at a 3 rather than lower.

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 44% and the description only maps to city, rent, beds and size via the opening sentence. It adds no meaning for sort, limit, cursor, is_guildhall or include_inactive, leaving nearly half the parameters reliant on the schema alone.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States the specific verb 'Find' and resource 'Tibia houses and guildhalls', enumerating the filterable fields (city, rent, beds, size). This clearly distinguishes it from sibling finders like tibia_find_creatures or tibia_find_items, though it doesn't name a sibling explicitly.

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?

Provides a concrete example question ('cheapest house in Thais with two beds') that shows typical usage, and directs the agent to tibia_get for positional details of a specific title. No explicit when-not guidance, but the use case is unambiguous.

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

Deploy Server