Skip to main content
Glama

Buy credits with a coin

get_credits

Starts a ChangeNOW swap for a get_credits_quote and returns order_id, pay_in_address (+ extra_id), the exact amount and expires_at. Credits are added automatically once the TFUEL arrives; poll get_credits_status. Needs sign-in (auth_challenge then auth_verify). At most 3 open orders and 10 a day.

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": "get_credits"
  }
}

Input Schema

NameRequiredDescriptionDefault
quote_idYesThe quote_id returned by get_credits_quote
accept_termsNotrue on your first order to accept the terms (v2)
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. Changed4 schema fields changed
    • addedInput schema / properties / accept_terms / default
      Added value: +false
    • addedInput schema / properties / accept_terms / description
      Added value: +"true on your first order to accept the terms (v2)"
    • addedInput schema / properties / quote_id / description
      Added value: +"The quote_id returned by get_credits_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.4/5.0
Behavior5/5

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

Beyond the annotations, it discloses that this starts an external ChangeNOW swap, credits are added automatically only after TFUEL arrives, and the caller should poll get_credits_status. It also documents authentication requirements and order-rate constraints, which are important behavioral details for a non-idempotent open-world mutation.

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?

The description is compact and front-loads the core action and return values. It is dense but generally well structured, with only a slightly awkward phrase 'for a get_credits_quote'.

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?

The tool has no output schema, but the description explains the key returned fields: order_id, pay_in_address with extra_id, exact amount, and expires_at. It also covers the follow-up polling flow, authentication prerequisites, and rate limits, so an agent has enough information to invoke and manage the tool.

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?

The input schema has 100% description coverage, so the schema already explains quote_id, refund_address, and accept_terms. The description adds only limited parameter meaning by linking quote_id to get_credits_quote and implying refund_address behavior indirectly through the swap context.

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 action: it starts a ChangeNOW swap for a credit purchase and returns concrete order details. It clearly distinguishes this from the quote and status tools by naming get_credits_quote as the source of quote_id and get_credits_status as the polling tool.

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 sequencing guidance: use a get_credits_quote result, poll get_credits_status afterward, and complete auth_challenge then auth_verify before calling. It also states rate limits of 3 open orders and 10 per day. It does not explicitly state when not to use the tool, but the alternatives are effectively named.

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