Lists currencies defined in a save, backpack templates, and each character template’s starting backpack contents, returning null when a character carries no backpack.
List the currencies defined in a save, its backpack templates, and what the character template's backpack holds at the start (null when characters carry no backpack).
| Name | Required | Description | Default |
|---|---|---|---|
| mapPath | No |
Changes observed during successful MCP inspections.
v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered structurally. The description adds useful return-content context — that results span save currencies, backpack templates, and starting backpack contents, with null meaning no backpack. It says nothing about ordering, pagination, or error behavior if no save is loaded.
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 the core action front-loaded and no filler. The embedded parenthetical listing three result categories is dense but each clause carries information; slightly smoother phrasing would earn a 5.
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?
With no output schema, the description carries the burden of explaining return values, and it does partially by naming the three currency sources and null semantics. However, the sole input parameter is left entirely unexplained, leaving the definition incomplete for correct invocation.
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 0% and 'mapPath' has no description anywhere, yet the description never mentions it — the agent cannot tell whether it targets a specific map, whether it is optional, or what happens when omitted. With only one parameter and no compensating text, the semantic gap is the whole schema.
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?
Opens with a specific verb+resource ('List the currencies') and scopes it to save-defined currencies, backpack templates, and the character template's starting backpack. This clearly separates it from the sibling 'scene_add_currency'. The trailing parenthetical about null backpacks is slightly convoluted but does not obscure the purpose.
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?
There is no statement of when to use this versus alternatives — the obvious sibling 'scene_add_currency' is never referenced, nor is any prerequisite (e.g., whether a map must be loaded). The agent can infer it is the read companion to scene_add_currency, but nothing in the text guides that choice.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.