Skip to main content
Glama

Start a TFUEL swap

tfuel_swap

Starts the ChangeNOW swap for a tfuel_swap_quote; the payout is always your signed-in Theta address. Returns status_id, pay_in_address (+ extra_id), the exact amount and the deadline; poll tfuel_swap_status. Needs sign-in (auth_challenge then auth_verify). 10 orders per hour.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "quote_id": "<quote_id>",
      "refund_address": "<refund_address>"
    },
    "name": "tfuel_swap"
  }
}

Input Schema

NameRequiredDescriptionDefault
quote_idYesThe quote_id returned by tfuel_swap_quote
refund_addressYesYour own address on the pay-in coin's chain; ChangeNOW refunds go only there

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / quote_id / description
      Added value: +"The quote_id returned by tfuel_swap_quote"
    • addedInput schema / properties / refund_address / description
      Added value: +"Your own address on the pay-in coin's chain; ChangeNOW refunds go only there"
  2. First observed

TDQS

A4.7/5.0
Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already mark this as non-read-only, open-world, non-idempotent and non-destructive, and the description adds genuinely new behavior: the payout always goes to the signed-in Theta address regardless of input, there is a deadline, and there is a hard rate cap of 10 orders per hour. That is materially more than the annotations convey.

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

Conciseness5/5

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

A single dense sentence pair with zero filler: purpose first, then the returned fields, then the next tool, then auth and rate-limit constraints. Every clause carries operational information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

There is no output schema, so the description takes responsibility for naming the return values (status_id, pay_in_address plus extra_id, amount, deadline), which it does. Combined with auth requirements and rate limits, an agent has everything needed to invoke and continue correctly.

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 100%, with both quote_id and refund_address fully documented in the schema, so the schema does the heavy lifting. The description's note that the payout address is fixed does clarify the boundary between payout and refund, but it does not add syntax or format detail beyond the schema. Baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description opens with a specific verb and resource ('Starts the ChangeNOW swap for a tfuel_swap_quote') and immediately scopes the payout destination. It reads clearly as the execution step in a quote-swap-status triad, distinct from tfuel_swap_quote and tfuel_swap_status.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It names the prerequisite chain explicitly ('Needs sign-in (auth_challenge then auth_verify)') and points to the follow-up tool ('poll tfuel_swap_status'), so an agent knows both how to qualify for the call and what to do afterward. The rate limit ('10 orders per hour') further constrains when the call can be repeated.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources