Confirms and executes a token conversion using a previously received quote ID, so you can complete a quoted crypto swap at the agreed terms.
The API confirms and executes a token conversion using a previously received quote ID.
| Name | Required | Description | Default |
|---|---|---|---|
| quoteId | Yes | Quote ID | |
| recvWindow | No | The value cannot be greater than 60000 |
Changes observed during successful MCP inspections.
v1.0.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the burden. It discloses that the tool executes a conversion, indicating a mutating operation, but does not mention irreversibility, invalid quote handling, or other consequences.
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?
One concise, front-loaded sentence with no wasted words. It effectively communicates the core action and prerequisite.
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 financial execution tool, the description is adequate but minimal. It doesn't explain return values or error conditions, and there is no output schema to fill the gap.
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 description coverage is 100% for both parameters, so the tool adds little beyond noting quoteId's role. The baseline of 3 is appropriate because the description does not provide extra parameter details.
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 specific verbs 'confirms and executes' and identifies the resource as a 'token conversion using a previously received quote ID'. This clearly distinguishes it from quote request or order status tools.
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?
It provides a clear prerequisite context ('previously received quote ID'), implying the tool is used after a quote request. However, it does not explicitly name alternatives or exclusions, so it stops short of a full 5.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.