tibiawiki-mcp

tibia_find_creatures

Read-only

Find Tibia creatures matching stat filters. Damage modifiers are percentages where 100 is neutral: "weak_to" means the creature takes MORE than 100% damage from that element, "resistant_to" means less. Use this for questions like "which creatures are weak to fire and give over 500 experience". Behaviour filters skip creatures whose value is unrecorded.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`sort`	No	experience, hitpoints and gold_per_kill: highest first.	experience
`limit`	No
`cursor`	No
`is_boss`	No
`weak_to`	No	Elements the creature takes extra damage from.
`pushable`	No
`summonable`	No	true: summon cost above 0. false: 0.
`paralysable`	No
`convinceable`	No	true: convince cost above 0. false: 0.
`resistant_to`	No
`hitpoints_max`	No	Creatures whose hitpoints are unrecorded are excluded from this filter.
`hitpoints_min`	No	Creatures whose hitpoints are unrecorded are excluded from this filter.
`bestiary_class`	No	e.g. "Dragon", "Human".
`bestiary_level`	No	Creatures with no recorded bestiary level are excluded from this filter.
`experience_max`	No
`experience_min`	No
`sees_invisible`	No
`include_inactive`	No
`location_contains`	No	Substring of the location text.

Output Schema

TableJSON Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedSep 26, 2026

addedOutput schema / properties / results / items / properties / raceId

Added value: +{
+  "description": "Tibia client race ID, not unique: some creatures share one, such as boss phases. null: the wiki records none.",
+  "type": [
+    "number",
+    "null"
+  ]
+}

changedOutput schema / properties / results / items / required

Previous value: -[
-  "title",
-  "name",
-  "hitpoints",
-  "experience",
-  "bestiaryClass",
-  "isBoss",
-  "modifiers",
-  "runsAt",
-  "seesInvisible",
-  "paralysable",
-  "pushable",
-  "summonCost",
-  "convinceCost",
-  "goldPerKill"
-]New value: +[
+  "title",
+  "name",
+  "hitpoints",
+  "experience",
+  "bestiaryClass",
+  "isBoss",
+  "modifiers",
+  "runsAt",
+  "seesInvisible",
+  "paralysable",
+  "pushable",
+  "summonCost",
+  "convinceCost",
+  "goldPerKill",
+  "raceId"
+]

Changed2 schema fields changedSep 25, 2026

addedOutput schema / properties / results / items / properties / name

Added value: +{
+  "description": "Name as the game prints it.",
+  "type": [
+    "string",
+    "null"
+  ]
+}

changedOutput schema / properties / results / items / required

Previous value: -[
-  "title",
-  "hitpoints",
-  "experience",
-  "bestiaryClass",
-  "isBoss",
-  "modifiers",
-  "runsAt",
-  "seesInvisible",
-  "paralysable",
-  "pushable",
-  "summonCost",
-  "convinceCost",
-  "goldPerKill"
-]New value: +[
+  "title",
+  "name",
+  "hitpoints",
+  "experience",
+  "bestiaryClass",
+  "isBoss",
+  "modifiers",
+  "runsAt",
+  "seesInvisible",
+  "paralysable",
+  "pushable",
+  "summonCost",
+  "convinceCost",
+  "goldPerKill"
+]

Changed16 schema fields changedSep 24, 2026

addedInput schema / properties / bestiary_level

Added value: +{
+  "description": "Creatures with no recorded bestiary level are excluded from this filter.",
+  "enum": [
+    "harmless",
+    "trivial",
+    "easy",
+    "medium",
+    "hard",
+    "challenging"
+  ],
+  "type": "string"
+}

addedInput schema / properties / convinceable

Added value: +{
+  "description": "true: convince cost above 0. false: 0.",
+  "type": "boolean"
+}

addedInput schema / properties / paralysable
```
Added value: +{
+  "type": "boolean"
+}
```
addedInput schema / properties / pushable
```
Added value: +{
+  "type": "boolean"
+}
```
addedInput schema / properties / sees_invisible
```
Added value: +{
+  "type": "boolean"
+}
```

addedInput schema / properties / sort / description

Added value: +"experience, hitpoints and gold_per_kill: highest first."

changedInput schema / properties / sort / enum

Previous value: -[
-  "experience",
-  "hitpoints",
-  "title"
-]New value: +[
+  "experience",
+  "hitpoints",
+  "title",
+  "gold_per_kill"
+]

addedInput schema / properties / summonable

Added value: +{
+  "description": "true: summon cost above 0. false: 0.",
+  "type": "boolean"
+}

addedOutput schema / properties / results / items / properties / convinceCost

Added value: +{
+  "description": "Mana. 0: cannot be convinced.",
+  "type": [
+    "number",
+    "null"
+  ]
+}

addedOutput schema / properties / results / items / properties / goldPerKill

Added value: +{
+  "description": "Estimated gross loot value at NPC prices. Drops without a recorded chance are left out, and items that sell only on the market count as 0.",
+  "type": [
+    "number",
+    "null"
+  ]
+}

addedOutput schema / properties / results / items / properties / paralysable
```
Added value: +{
+  "type": [
+    "boolean",
+    "null"
+  ]
+}
```
addedOutput schema / properties / results / items / properties / pushable
```
Added value: +{
+  "type": [
+    "boolean",
+    "null"
+  ]
+}
```

addedOutput schema / properties / results / items / properties / runsAt

Added value: +{
+  "description": "Hit points at which it flees. 0: never flees.",
+  "type": [
+    "number",
+    "null"
+  ]
+}

addedOutput schema / properties / results / items / properties / seesInvisible
```
Added value: +{
+  "type": [
+    "boolean",
+    "null"
+  ]
+}
```

addedOutput schema / properties / results / items / properties / summonCost

Added value: +{
+  "description": "Mana. 0: cannot be summoned.",
+  "type": [
+    "number",
+    "null"
+  ]
+}

changedOutput schema / properties / results / items / required

Previous value: -[
-  "title",
-  "hitpoints",
-  "experience",
-  "bestiaryClass",
-  "isBoss",
-  "modifiers"
-]New value: +[
+  "title",
+  "hitpoints",
+  "experience",
+  "bestiaryClass",
+  "isBoss",
+  "modifiers",
+  "runsAt",
+  "seesInvisible",
+  "paralysable",
+  "pushable",
+  "summonCost",
+  "convinceCost",
+  "goldPerKill"
+]

First observedSep 15, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true, and the description adds valuable behavior beyond that: damage modifiers are percentages where 100 is neutral, weak_to/resistant_to are defined precisely, and behavior filters skip creatures with unrecorded values. No contradiction with annotations.

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 sentences with no filler: purpose is front-loaded, followed by essential damage-modifier semantics, an example, and an edge-case behavior note. 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?

For a 19-parameter filter tool with an output schema and read-only annotation, the description covers core filter semantics and unrecorded-value behavior. It omits pagination/cursor and sort/limit details, but those are either in the schema or secondary for a first call.

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 only 47%, so the description must compensate. It explains the non-obvious weak_to/resistant_to semantics and the unrecorded-value behavior for filters. However, many parameters (cursor, limit, booleans, experience ranges) remain undocumented in both schema and description, so compensation is partial.

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 ('Find') and resource ('Tibia creatures') with 'matching stat filters', clearly distinguishing it from sibling find_items/spells/quests tools. The example query reinforces the exact 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?

Provides an explicit example use case ('which creatures are weak to fire and give over 500 experience'), giving clear context for when to use this tool. It does not name sibling alternatives or exclusions, but the resource-specific naming makes selection straightforward.

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.

tibia_find_creatures

Input Schema

Output Schema

Schema Changelog

TDQS

Glama MCP Gateway

Resources