Skip to main content
Glama

Quote credits for a coin

get_credits_quote
Read-onlyIdempotent

Returns a ChangeNOW quote for a Wave credits bundle paid with another coin: the exact coin amount, TFUEL Wave receives, the minimum, and a quote_id valid 10 minutes for get_credits. Use balance_claim if you already hold TFUEL. Free. Needs sign-in (auth_challenge then auth_verify). 1 quote per 5 s.

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>",
      "bundle": "<bundle>"
    },
    "name": "get_credits_quote"
  }
}

Input Schema

NameRequiredDescriptionDefault
bundleYesBundle in USD: 10, 25 or 50 (2,500 / 7,000 / 15,000 credits)
pay_withYesThe coin you pay with (ChangeNOW ticker)

Output Schema

NameRequiredDescriptionDefault
blockNo
staleNo
amountNo
sourceNo
quote_idNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • addedInput schema / properties / bundle / description
      Added value: +"Bundle in USD: 10, 25 or 50 (2,500 / 7,000 / 15,000 credits)"
    • addedInput schema / properties / pay_with / description
      Added value: +"The coin you pay with (ChangeNOW ticker)"
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "additionalProperties": true,
      +  "properties": {
      +    "amount": {
      +      "type": [
      +        "number",
      +        "string"
      +      ]
      +    },
      +    "block": {
      +      "type": [
      +        "integer",
      +        "null"
      +      ]
      +    },
      +    "quote_id": {
      +      "type": "string"
      +    },
      +    "source": {
      +      "type": "string"
      +    },
      +    "stale": {
      +      "type": "boolean"
      +    }
      +  },
      +  "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 declare readOnlyHint, idempotentHint, openWorldHint and non-destructive, and the description goes beyond them with concrete operating facts: the quote is free, the quote_id expires in 10 minutes, and there is a 1-per-5-second throttle. It does not describe failure modes (e.g. what happens if a bundle/coin pair is unsupported), which keeps it just short of the top.

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 return payload and the get_credits dependency are front-loaded, then cost, auth and rate limit follow in short fragments. Nothing is wasted, though the telegraphic 'Free. Needs sign-in... 1 quote per 5 s.' style reads as staccato notes rather than prose.

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 two-parameter read-only quote tool with an output schema, the description covers everything an agent needs to call it correctly: auth prerequisite, cost, throttling, quote lifetime, and the downstream tool that consumes quote_id. No significant gap remains.

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%: both parameters are documented enums with credit-amount mappings for each bundle. The description only adds the framing that pay_with is 'another coin' (i.e. not TFUEL), which is marginally useful but mostly repeats what the schema already supplies.

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?

States a specific verb and resource (returns a ChangeNOW quote for a Wave credits bundle paid with another coin) and enumerates what the response carries: coin amount, TFUEL received, minimum, and a quote_id. It also names the consuming sibling (get_credits) and the alternative (balance_claim), so an agent can place it among get_credits, tfuel_swap_quote and quote without opening a schema.

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?

Gives an explicit exclusion-plus-alternative: 'Use balance_claim if you already hold TFUEL.' It also names the prerequisite flow (auth_challenge then auth_verify) and the rate limit, so the agent knows both when to pick this tool and what must happen before calling it.

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