Skip to main content
Glama

TFUEL swap status

tfuel_swap_status
Read-onlyIdempotent

Returns the status of a tfuel_swap by the status_id tfuel_swap returned: waiting, confirming, exchanging, sending, finished, failed, refunded, expired or cancelled, and the Theta payout tx once sent. Poll at most every 30 s. Read-only; needs sign-in as the wallet that made the swap.

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": {
      "status_id": "<status_id>"
    },
    "name": "tfuel_swap_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
status_idYesThe status_id returned by tfuel_swap (24 url-safe characters)

Output Schema

NameRequiredDescriptionDefault
blockNo
staleNo
sourceNo
statusNo
payout_hashNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / status_id / description
      Added value: +"The status_id returned by tfuel_swap (24 url-safe characters)"
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "additionalProperties": true,
      +  "properties": {
      +    "block": {
      +      "type": [
      +        "integer",
      +        "null"
      +      ]
      +    },
      +    "payout_hash": {
      +      "type": "string"
      +    },
      +    "source": {
      +      "type": "string"
      +    },
      +    "stale": {
      +      "type": "boolean"
      +    },
      +    "status": {
      +      "enum": [
      +        "waiting",
      +        "confirming",
      +        "exchanging",
      +        "sending",
      +        "finished",
      +        "failed",
      +        "refunded",
      +        "expired",
      +        "cancelled"
      +      ],
      +      "type": "string"
      +    }
      +  },
      +  "type": "object"
      +}
  2. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already cover read-only, idempotent, and non-destructive behavior, and the description adds two things they don't: an authorization constraint ('needs sign-in as the wallet that made the swap') and a polling rate limit. 'Read-only' merely restates readOnlyHint=true, which is the only redundancy.

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

Conciseness4/5

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

Three short sentences with the return content front-loaded and no filler; the polling and auth constraints follow compactly. The phrasing 'by the status_id tfuel_swap returned' is slightly awkward and the long status list is dense, but nothing is wasted.

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?

For a single-parameter read tool with an output schema and rich annotations, the description covers what an agent still needs: the meaning of each status value, the payout tx field, the polling limit, and the sign-in requirement. Nothing material is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the 24-character format is already documented, establishing a baseline of 3. The description adds provenance by tying status_id to the value returned by tfuel_swap, which tells the agent where to obtain the parameter, but it adds no further syntax detail.

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 states a specific verb and resource (returns the status of a tfuel_swap) and enumerates the exact result values (waiting through cancelled) plus the Theta payout tx. That level of detail lets an agent distinguish it from tfuel_swap and tfuel_swap_quote without opening any schema.

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

Usage Guidelines4/5

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

The description makes the usage pattern explicit with 'Poll at most every 30 s', which tells the agent both that this is a polling tool and what cadence is acceptable. It doesn't name a sibling alternative or say when not to call it, so it falls just short of a 5.

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