tibiawiki-mcp

Overview Schema Source Related Servers Discussions Admin

tibia_find_offers

Read-only

Find NPC trade offers and prices filtered by NPC, item, buy/sell direction, or currency, so you can answer questions like what Rashid buys or what costs Gold Tokens.

Instructions

Find NPC trade offers with prices by NPC, item, direction and currency, e.g. "everything Rashid buys" or "what costs Gold Tokens".

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

Input Schema

Name	Required	Description
`npc`	No	Exact title, any case.
`item`	No	Exact title, any case.
`limit`	No
`cursor`	No
`currency`	No	e.g. "Gold Coin", any case.
`direction`	No	sell: the NPC sells to the player. buy: the NPC buys from the player.
`include_inactive`	No	Include inactive items.

Output Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

Addedv0.22.0Nov 5, 2026

TDQS

A3.6/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 and locality are covered. The description adds nothing about pagination via cursor, the 100-result cap, or how include_inactive affects results, which are the behaviors an agent would actually need disclosed.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single front-loaded sentence that states the resource and then illustrates it with two recognizable queries; nothing is wasted. It is short to the point of leaving out operational detail.

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-value shape need not be explained, and annotations cover the read-only profile. For a 7-parameter search tool, only pagination/limit behavior is left unexplained, which is a modest gap rather than a blocking one.

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 71%, so most parameters are already documented, and the description echoes npc, item, direction and currency without adding syntax or format detail. The example 'Gold Coin' gives a small hint about currency values, but limit, cursor and include_inactive remain undescribed in both places.

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 (Find) plus resource (NPC trade offers with prices) and the filterable dimensions, which is more precise than the sibling tibia_find_* lookups. It does not, however, explicitly differentiate itself from close neighbors like tibia_where_to_sell or tibia_how_to_obtain.

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 two quoted examples ('everything Rashid buys', 'what costs Gold Tokens') give concrete selection contexts that map cleanly to the npc/direction and currency parameters. There is no explicit when-not-to-use or named alternative, which keeps it below a 5.

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

Deploy Server