Skip to main content
Glama

Aquedra Run

Buy credits

buy_credits

Buy a pack of Aquedra Run credits (US$5, US$20, US$50, US$100; 1 credit = US$1), only when the user asked for it or authorized their wallet to spend. With method "card" the result has a checkout_url the person completes in their browser; this tool never charges a card. With method "usdc" and no payment, the result is an x402 payment request (isError, PaymentRequired in structuredContent); an x402 wallet pays by calling this tool again with the same arguments and the signed payment in params._meta["x402/payment"], and the result's _meta["x402/payment-response"] carries the settlement. If a result says a payment is pending, do not pay again: call again with the same payment.

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": {
      "pack_usd": "<pack_usd>"
    },
    "name": "buy_credits"
  }
}

Input Schema

NameRequiredDescriptionDefault
methodNocard returns a checkout_url the person pays in their browser; usdc pays over x402.card
pack_usdYesCredit pack in US dollars; 1 credit = US$1.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.9/5.0
Behavior5/5

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

Annotations only say this is not read-only, is open-world, and is not idempotent; the description goes well beyond that by stating the tool never charges a card itself, that card mode returns a checkout_url for the human, that usdc mode returns an isError/PaymentRequired x402 request, and where settlement appears. The pending-payment retry rule is exactly the kind of behavioral detail annotations cannot express.

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?

It is front-loaded with the purchase intent and price list before the mechanics, and every clause carries operational information. It is, however, a dense run of compound sentences with nested parentheticals and quoted keys, which makes it slower to parse than it needs to be for a two-parameter tool.

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?

There is no output schema, yet the description covers both payment flows end to end: how card mode resolves, how usdc mode signals PaymentRequired, how to resubmit with the signed payment, and how to read settlement. Nothing an agent needs in order to invoke it correctly, or to avoid double-paying, is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Although schema coverage is 100%, the description adds meaning the schema cannot: it explains the consequence of each method value and documents an argument that is not in the schema at all, params._meta["x402/payment"], plus the response-side _meta["x402/payment-response"] settlement field. That is substantial semantics beyond the structured input definition.

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?

"Buy a pack of Aquedra Run credits" gives a specific verb and resource, then immediately names the concrete pack denominations (US$5/20/50/100) and the 1 credit = US$1 conversion. No sibling tool in the list performs a purchase, so an agent can route this 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 Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It states an explicit precondition ("only when the user asked for it or authorized their wallet to spend") and an explicit retry rule ("If a result says a payment is pending, do not pay again: call again with the same payment"). It also distinguishes the two modes: card hands off to a browser checkout, usdc requires a second call carrying the signed payment.

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