Skip to main content
Glama

Quote for buying credits with a plain USDC transfer (free)

credits_quote

FREE. Step 1 of buying a credits pack from any wallet: returns the exact USDC amount (price + a random tail under $0.01), the receiving address on Base, a secret quote id and a 60-minute window. Then send exactly that amount and call credits_claim.

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": {
      "from": "<from>"
    },
    "name": "credits_quote"
  }
}

Input Schema

NameRequiredDescriptionDefault
fromYesThe 0x wallet you will send USDC from (the quote is bound to it)
packNostarter ($0.25), class ($1.00) or term ($5.00); default starter

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Annotations only say readOnlyHint=false, openWorldHint=false, idempotentHint=false, destructiveHint=false. The description adds substantial context beyond that: the call is free, the quoted amount carries a random sub-$0.01 tail, the quote is time-boxed to 60 minutes, and it is bound to the sending wallet. Those traits directly affect how an agent must use the result.

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?

Two tight sentences, front-loaded with 'FREE' and the step ordering, followed by the exact sequence of next actions. Every clause carries operational information; nothing is redundant.

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?

No output schema exists, and the description fully enumerates the returned values (amount, receiving address on Base, quote id, expiry window). Combined with the follow-up instruction, an agent has everything needed to invoke and act on the result.

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 already documents both parameters, including the pack enum and prices. The description reinforces that the quote is wallet-bound and that the amount includes a random tail, but adds no syntax or format detail beyond the schema, so the baseline 3 applies.

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 exact USDC amount... receiving address... quote id... 60-minute window') and frames itself as 'Step 1 of buying a credits pack,' which cleanly separates it from credits_claim (step 2). An agent can identify the tool's output without opening the schema.

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?

Explicitly says this is the first step for 'any wallet' doing a plain USDC transfer and names the follow-up action ('send exactly that amount and call credits_claim'). It does not state when to prefer this over other payment siblings such as payment_options or buy_credit_pack, so the routing guidance is clear but not exhaustive.

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