Skip to main content
Glama

Quote a CREDIT purchase

quote_credit_purchase
Read-only

Fund your account with USDG: a live quote for buying CREDIT with USDG on Orbio's exchange, plus three unsigned transactions for your owner wallet to sign and send in order (approve USDG, buy CREDIT to your wallet, send it to the deposit address). Octio never holds your USDG and signs nothing. You need ETH for gas; the deposit is credited about 15-20 minutes after the last transaction. Free; needs an API key, whose owner wallet it quotes for.

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": {
      "usdg": "<usdg>"
    },
    "name": "quote_credit_purchase"
  }
}

Input Schema

NameRequiredDescriptionDefault
usdgYesUSDG to spend as a decimal string, e.g. "5" (at most 10000, 6 decimals)
slippage_bpsNoAccepted slippage in basis points; defaults to 100 (1%)

Output Schema

NameRequiredDescriptionDefault
notesYes
quoteYes
walletYes
chain_idYes
slippage_bpsYes
transactionsYes
min_credit_outYes
deposit_addressYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior5/5

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

Adds substantial behavior beyond the annotations: no custody of USDG, nothing signed server-side, gas requirement, a 15-20 minute crediting window after the last transaction, and that the call is free. These details are consistent with readOnlyHint=true and idempotentHint=false (a live quote is naturally non-idempotent).

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?

Front-loaded with the core action and the returned transactions, then prerequisites and timing. It is one dense passage with a long parenthetical listing the transaction sequence, which is useful but slightly heavy to scan.

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?

With an output schema, full annotation coverage, and 100% parameter documentation, the definition covers what an agent still needs: cost, prerequisites, custody model, and settlement latency. Only the sequencing/slippage tradeoff of the signed transactions is left implicit.

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 coverage is 100% and the schema already documents the usdg amount format and the slippage_bps default, so the schema carries the load. The description only implies that usdg is the spend amount and says nothing about slippage, which is the baseline-3 case.

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 ('live quote for buying CREDIT with USDG on Orbio's exchange') and goes further by naming the exact return payload: three unsigned transactions to sign in order. An agent knows precisely what comes back and can distinguish this from account-reading siblings like get_balance.

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 clear context for use ('Fund your account with USDG') plus prerequisites (API key, ETH for gas) and outcome timing. It does not name an alternative tool or state when not to use it, 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