Skip to main content
Glama

Buy Dagon credits with Solana USDC

dagon_buy_credits
Destructive

Purchase Dagon Inference credits with USDC on Solana by verifying the treasury payment and either signing/submitting the transaction or returning an unsigned transaction for your payer wallet.

Instructions

Buy credits for the configured Dagon account, paid in USDC on Solana. The server checks that the gateway's transaction is exactly the USDC payment to the configured treasury (DAGON_TREASURY_WALLET). If the MCP server has a wallet (DAGON_WALLET_SECRET_KEY), it then signs and confirms it (submitting it itself unless the purchase is fee sponsored, in which case the payment service adds the fee payer's signature and submits it). Otherwise it returns the verified unsigned transaction for payer_wallet to sign; then call dagon_confirm_purchase with signed_transaction (fee sponsored: do not submit it yourself) or with the signature of the transaction you submitted (not fee sponsored).

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": {
      "amount_usd": "<amount_usd>"
    },
    "name": "dagon_buy_credits"
  }
}

Input Schema

NameRequiredDescriptionDefault
chainNoPayment chain. Only 'solana' (USDC) is supported.solana
amount_usdYesAmount to buy in USD (whole cents, e.g. 5 or 12.5).
payer_walletNoBase58 Solana address that pays. Required when the server has no wallet configured.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already flag destructive/openWorld/non-idempotent, and the description goes well beyond that: it discloses that the server validates the gateway transaction is exactly the USDC payment to DAGON_TREASURY_WALLET, who signs and submits under each configuration, and that fee-sponsored transactions must not be submitted by the caller. Those are exactly the operational traits an agent cannot infer from the schema or annotations.

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?

Purpose and payment rail are front-loaded, and every clause carries a condition the caller must act on, including the parenthetical about not submitting a fee-sponsored transaction. It is dense and requires careful reading of nested conditions, but there is no filler to cut.

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 payment tool with no output schema, the description covers the verification step, both signing paths, and the required follow-up call with the argument to pass in each case, which is what an agent needs to complete the flow. The main unstated item is that spending is irreversible and retries may double-charge, a gap partly covered by the destructive and non-idempotent annotations.

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%, so the baseline is 3, and the description adds real meaning on top: it explains why payer_wallet matters (it receives the unsigned transaction to sign) and ties signed_transaction's form to whether the purchase is fee sponsored. amount_usd and chain remain schema-only, but the payer branch is genuinely illuminated.

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?

The first sentence names a specific verb and resource ('Buy credits for the configured Dagon account') plus the payment rail ('USDC on Solana'), which no sibling (dagon_balance, dagon_chat, dagon_create_key) shares. The closing sentence explicitly hands off to dagon_confirm_purchase, so the boundary between the two tools is legible without opening either 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?

It states the two operating paths precisely: if DAGON_WALLET_SECRET_KEY exists, the server signs and confirms; otherwise it returns a verified unsigned transaction for payer_wallet to sign, after which dagon_confirm_purchase is called with a specific argument depending on fee sponsorship. That is clear conditional routing rather than generic guidance, but there is no explicit 'when not to use this' or note that a purchase is non-idempotent and should not be blindly retried.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.