tibiawiki-mcp

Overview Schema Source Related Servers Discussions Admin

tibia_find_quests

Read-only

Find Tibia quests that match a character's level, premium status, Rookgaard restriction, and location, including rewards. Use filters to answer questions about which quests a character can complete.

Instructions

Find Tibia quests by level, premium, Rookgaard and location, with their rewards. Use this for questions like "which quests can a level 20 character do". Call tibia_get with a title for the legend and dangers.

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

Input Schema

Name	Required	Description	Default
`sort`	No	Levels ascend, title is alphabetical. Unknown levels come last.	level_recommended
`limit`	No
`cursor`	No
`level_max`	No	Highest level the character has. Quests with no level requirement always match.
`is_premium`	No
`is_rookgaard`	No
`include_inactive`	No
`location_contains`	No	Literal substring of the location, case-insensitive.

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",
-  "location",
-  "levelRequired",
-  "levelRecommended",
-  "isPremium",
-  "estimatedTime",
-  "rewards"
-]New value: +[
+  "title",
+  "articleId",
+  "location",
+  "levelRequired",
+  "levelRecommended",
+  "isPremium",
+  "estimatedTime",
+  "rewards"
+]

Addedv0.10.0Sep 25, 2026

TDQS

A3.8/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 is covered. The description adds that results carry rewards and that deeper lore lives behind tibia_get — useful. It says nothing about pagination (limit/cursor exist), the default hiding of inactive quests, or ordering behavior beyond what the schema states.

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: capability and filter axes first, then a concrete example, then the follow-up route. Every sentence earns its place with 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 values needn't be described, and the description covers purpose plus the tibia_get handoff. The remaining gap is behavioral detail on the undocumented optional parameters (especially include_inactive's default of false), which could surprise an agent.

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 38% across 8 parameters. The description names the premium, Rookgaard and location axes, partly compensating, but never disambiguates is_premium (premium-only quests vs. premium account filter) and is silent on include_inactive, cursor and limit. Enough to orient, not enough to resolve ambiguity.

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?

Specific verb + resource ("Find Tibia quests") plus the filterable axes (level, premium, Rookgaard, location) and the fact that rewards are included. It is distinguishable from siblings, though it doesn't name a competing search tool — only tibia_get for follow-up detail.

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 concrete triggering question ("which quests can a level 20 character do") and an explicit handoff: "Call tibia_get with a title for the legend and dangers." That's clear routing for the follow-up case, but there are no exclusions or guidance for when other tibia_find_* tools are the better choice.

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

Deploy Server