list_tradersList all Escape from Tarkov traders, showing each trader's currency and next restock time. Plan your purchases by checking trader schedules.
List all Escape from Tarkov traders with their currency and next restock/reset time.
| Name | Required | Description | Default |
|---|---|---|---|
| lang | No | Language for names/descriptions. Defaults to "en". | |
| gameMode | No | Game mode to query. Defaults to the server's configured game mode ("regular"). |
Changes observed during successful MCP inspections.
v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the behavioral burden, but the verb 'List' clearly signals a read-only operation. It adds concrete output expectations (currency, restock/reset time) without needing to warn about side effects since none are plausible for a listing operation.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
A single sentence with no redundant words; the core action and the two key output fields are front-loaded. Every part earns its place.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a low-complexity list tool, the description plus fully described schema is sufficient to call it correctly. It lacks a note about response shape, but the stated fields (currency and reset time) cover the main return expectations.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 100% and both parameters (lang, gameMode) have enum values and descriptions in the schema. The tool description adds no parameter-specific meaning, so the baseline score of 3 applies.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description uses a specific verb ('List') and resource ('all Escape from Tarkov traders'), and adds the output fields (currency, next restock/reset time). This clearly distinguishes it from singular sibling get_trader and other list tools like list_hideout_stations.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The plural scope and 'all' imply use when a complete trader overview is needed, but the description never states when not to use it or points to get_trader for a single trader. Usage guidance is only implied, not explicit.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.