Skip to main content
Glama

Quote a TFUEL swap

tfuel_swap_quote
Read-onlyIdempotent

Returns a ChangeNOW quote to swap another coin into TFUEL or THETA paid to your own signed-in address (no credits involved): the exact coin amount, what arrives and a quote_id for tfuel_swap. Give usd or amount. Free. Needs sign-in (auth_challenge then auth_verify).

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": {
      "pay_with": "<pay_with>"
    },
    "name": "tfuel_swap_quote"
  }
}

Input Schema

NameRequiredDescriptionDefault
getNoWhat you receive (default tfuel)tfuel
usdNoUSD value of TFUEL/THETA to receive, up to 500
amountNoOr the exact amount of pay_with coin you'll send
pay_withYesThe coin you pay with (ChangeNOW ticker)

Output Schema

NameRequiredDescriptionDefault
blockNo
staleNo
sourceNo
quote_idNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed8 schema fields changed
    • addedInput schema / properties / amount / description
      Added value: +"Or the exact amount of pay_with coin you'll send"
    • addedInput schema / properties / amount / minimum
      Added value: +0
    • addedInput schema / properties / get / default
      Added value: +"tfuel"
    • addedInput schema / properties / pay_with / description
      Added value: +"The coin you pay with (ChangeNOW ticker)"
    • addedInput schema / properties / usd / description
      Added value: +"USD value of TFUEL/THETA to receive, up to 500"
    • addedInput schema / properties / usd / maximum
      Added value: +500
    • addedInput schema / properties / usd / minimum
      Added value: +0
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "additionalProperties": true,
      +  "properties": {
      +    "block": {
      +      "type": [
      +        "integer",
      +        "null"
      +      ]
      +    },
      +    "quote_id": {
      +      "type": "string"
      +    },
      +    "source": {
      +      "type": "string"
      +    },
      +    "stale": {
      +      "type": "boolean"
      +    }
      +  },
      +  "type": "object"
      +}
  2. First observed

TDQS

A4.2/5.0
Behavior4/5

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

The annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint=false. The description adds meaningful behavior beyond those annotations: authentication is required, no credits are involved, the quote is free, funds go to the signed-in address, and the response includes a quote_id for tfuel_swap.

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?

The description is compact and front-loaded: it states what is returned, what it is for, how to specify the amount, that it is free, and that sign-in is needed. Every clause contributes useful information.

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

Completeness4/5

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

The description is largely complete for a read-only quote tool: it covers purpose, auth requirements, amount selection, credit exclusion, and the returned quote_id. It could be slightly more complete by noting quote expiration or time sensitivity, but the output schema can carry return details.

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 description coverage is 100%, so the input schema already explains get, usd, amount, and pay_with. The description only restates 'Give usd or amount' and does not add substantially more parameter semantics beyond the schema.

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 uses a specific verb and resource: it returns a ChangeNOW quote to swap another coin into TFUEL or THETA. It also distinguishes the operation from credit-based swaps by saying 'no credits involved' and identifies the downstream sibling by providing a quote_id for tfuel_swap.

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?

It gives clear usage context: supply usd or amount, the quote is free, and sign-in is required via auth_challenge then auth_verify. It implies this quote precedes tfuel_swap, but it does not explicitly state when not to use it or compare it directly with the generic quote sibling.

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