tibiawiki-mcp

Overview Schema Source Related Servers Discussions Admin

tibia_find_updates

Read-only

Find Tibia game updates by matching text in titles, summaries, and change lists, filtered by release date and returned newest first. Use it to answer questions like what changed for knights in 2026.

Instructions

Find Tibia game updates by text and release date, for questions like "what changed for knights in 2026" or "which update added X". Matches the text, case-insensitive for ASCII letters, in an update's title, name, summary and change list, newest first, and returns the matching change lines. For the full changes, call tibia_get with type "update" and the returned title.

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

Input Schema

Name	Required	Description
`text`	No	Literal substring, e.g. "knight".
`limit`	No
`cursor`	No
`released_after`	No	YYYY-MM-DD, inclusive.
`released_before`	No	YYYY-MM-DD, inclusive.

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",
-  "name",
-  "releaseDate",
-  "version",
-  "updateType",
-  "summary",
-  "matchingLines"
-]New value: +[
+  "title",
+  "articleId",
+  "name",
+  "releaseDate",
+  "version",
+  "updateType",
+  "summary",
+  "matchingLines"
+]

Addedv0.7.0Sep 23, 2026

TDQS

A4.8/5.0

Behavior5/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, and the description is consistent with a safe local read. Beyond that it discloses the matching rule (case-insensitive for ASCII letters), the fields searched (title, name, summary, change list), the sort order (newest first), and that the response is matching change lines rather than whole updates — genuine behavioral detail not present in the 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?

Two sentences, both front-loaded: the capability and its filters come first, the escalation path to tibia_get comes last. Every clause carries information an agent would otherwise have to guess.

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?

With an output schema present, the description need not spell out return shape, and it still notes that matching change lines are returned. The remaining gap is pagination: cursor and limit are unaddressed in both the description and the schema, so an agent may not realize it must follow a cursor for complete results.

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?

At 60% schema coverage, the description compensates well for the undocumented parameters: it explains that "text" is matched against title/name/summary/change list (the schema only says "literal substring") and that release-date bounds act as filters with newest-first ordering. It does not explain limit or cursor semantics, so it falls short of full 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 Tibia game updates") plus the two dimensions it filters on (text and release date), and the two example questions make the intended query shape unambiguous. It is clearly distinct from siblings like tibia_find_creatures or tibia_get without needing their schemas.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives concrete triggering questions ("what changed for knights in 2026", "which update added X") and an explicit handoff: "For the full changes, call tibia_get with type "update" and the returned title." That names the alternative and the condition that selects it, which is exactly the when/when-not routing an agent needs.

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

Deploy Server