Cancel your trade offer (Cancels the trade you initiated. Items are returned to you.)
| Name | Required | Description | Default |
|---|---|---|---|
| trade_id | Yes | UUID of the trade offer | |
| session_id | Yes | Your session ID from login/register |
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The description states this tool cancels a trade and returns items, which are mutating actions. However, the annotations declare readOnlyHint: true, directly contradicting the described behavior. This is a serious inconsistency, making the behavioral transparency score a 1 due to the annotation contradiction.
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?
The description is a single sentence that directly states the action and the result, with no redundant wording. It is perfectly concise and front-loaded.
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?
The description covers the essential behavior of canceling a trade and returning items, and the schema fully documents parameters. However, it doesn't address failure scenarios (e.g., trade already accepted or nonexistent) and is undermined by the contradictory readOnlyHint annotation, so it is adequate but not complete.
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?
The input schema covers both parameters (trade_id and session_id) with descriptions, achieving 100% schema coverage. The description does not add additional parameter semantics, so the baseline of 3 is appropriate.
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 clearly states the action ('Cancel your trade offer') and specifies it applies to trades the user initiated, with the outcome that items are returned. This is a specific verb+resource combination that distinguishes it from siblings like trade_offer, trade_accept, and trade_decline.
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 description clearly indicates when to use this tool: to cancel a trade you initiated. It doesn't explicitly mention alternatives or exclusions, but the phrase 'the trade you initiated' provides context that helps differentiate from tools like trade_decline (for rejecting incoming offers).
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Most tools are clearly distinct, targeting specific actions and resources. A few overlaps exist (e.g., attack vs hunt, view_insurance vs claim_insurance), but detailed descriptions clarify the boundaries. The scale makes selection harder, but each tool has a clear purpose.
The majority use a consistent verb_noun snake_case pattern (e.g., create_buy_order, get_cargo, accept_mission). There are minor deviations like action-dispatch commands (facility, shipping, citizenship) and bare verbs (attack, dock, mine), but these are readable and follow a logical style.
With 212 tools, the server far exceeds any reasonable scope for an MCP. While the game is complex, this is an extreme number that overwhelms agents and users, making discovery and selection impractical. The calibration considers 25+ already too many, and 212 is extreme.
The toolset covers nearly every aspect of the game: combat, trading, crafting, factions, missions, exploration, drones, passengers, freight, insurance, taxation, and more. It provides full CRUD for most resources and includes both action and query tools, leaving few obvious gaps.
