Skip to main content
Glama

Credits order status

get_credits_status
Read-onlyIdempotent

Returns the status of a get_credits order by the order_id get_credits returned. Status is one of waiting, confirming, exchanging, sending, finished, failed, refunded, expired, cancelled; it also returns ChangeNOW's payout tx and credits_added once Wave credits your balance. Poll at most every 30 s. Read-only; needs sign-in as the wallet that made the order.

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": {
      "order_id": "<order_id>"
    },
    "name": "get_credits_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
order_idYesThe order_id returned by get_credits, e.g. swp_...

Output Schema

NameRequiredDescriptionDefault
blockNo
staleNo
sourceNo
statusNo
order_idNo
payout_hashNo
credits_addedNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / order_id / description
      Added value: +"The order_id returned by get_credits, e.g. swp_..."
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "additionalProperties": true,
      +  "properties": {
      +    "block": {
      +      "type": [
      +        "integer",
      +        "null"
      +      ]
      +    },
      +    "credits_added": {
      +      "type": "integer"
      +    },
      +    "order_id": {
      +      "type": "string"
      +    },
      +    "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.6/5.0
Behavior5/5

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

Beyond the annotations (which already declare read-only, idempotent, non-destructive, open-world), the description discloses auth scope ('needs sign-in as the wallet that made the order'), a rate/polling limit, the full terminal and intermediate status set, and the conditional fields (payout tx, credits_added) that only appear after crediting. That is meaningful behavior the structured fields do not carry.

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 sentences, front-loaded with purpose, then statuses, then operational constraints — no filler. The long inline status enumeration is somewhat bulky and partially overlaps what the output schema can express, keeping it from a 5.

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?

An output schema exists, so return values need not be re-explained, and the description still covers the pieces that matter for correct invocation: where the ID comes from, auth requirements, polling cadence, and when extra fields appear. Nothing an agent needs to call this correctly 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% and the single parameter already has an example, so the baseline is 3, but the description adds provenance ('the order_id returned by get_credits'), which tells the agent where the value must originate rather than merely its type.

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 the status of a get_credits order') plus the keying input ('by the order_id get_credits returned'), which cleanly separates it from get_credits itself. The enumerable status space is also named, so an agent knows exactly what kind of answer to expect.

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?

Gives a concrete prerequisite (order_id must come from a prior get_credits call) and an explicit polling constraint ('at most every 30 s'), which is real operational guidance. It does not name a when-not or point to an alternative status tool such as tfuel_swap_status for other swap flows, so it stops short of full routing guidance.

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