Skip to main content
Glama

Buy Dagon credits with Solana USDC

dagon_buy_credits

Start a credit purchase for the connection's Dagon key, paid in USDC on Solana from payer_wallet (POST /v1/credits/purchase). This server never signs: it returns the unsigned transaction for payer_wallet to sign. Submit it to Solana yourself, then pass its signature to dagon_confirm_purchase. The wallet pays the Solana network fee (under $0.01), so it needs at least 0.0005 SOL besides the USDC.

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>",
      "payer_wallet": "<payer_wallet>"
    },
    "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_walletYesBase58 Solana address that pays and signs.

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 flag it as a non-read-only, non-idempotent, open-world, non-destructive call; the description adds the crucial behavior that the server never signs and only returns an unsigned transaction for the wallet to sign. It also discloses the Solana network fee (<$0.01) and the minimum SOL balance required, which an agent cannot infer from annotations alone.

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?

Four tight sentences, front-loaded with the action and the amount/asset, then the signing model, then the next step and the balance prerequisite. Every sentence carries information the agent needs and none 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?

There is no output schema, but the description covers the return value (an unsigned transaction), the caller's obligations, and the follow-on call required to finish the purchase. For a non-idempotent, open-world purchase tool this is sufficiently complete.

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 description coverage is 100%, so amount_usd, payer_wallet, and the chain constant are already fully documented in the schema. The description reinforces that payment is USDC on Solana from payer_wallet but adds no format or constraint detail beyond what the schema already states, 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?

The description gives a specific verb and resource ("Start a credit purchase for the connection's Dagon key"), the payment asset and chain (USDC on Solana), and the funding source (payer_wallet). It also names the follow-up sibling dagon_confirm_purchase, so an agent can place this tool in the workflow without opening another 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?

Usage context is explicit: this starts a purchase, the server returns an unsigned transaction, the caller must submit it to Solana itself and then call dagon_confirm_purchase with the signature. The preconditions (wallet needs 0.0005 SOL for fees) are stated. No explicit when-not-to-use or alternative purchase path is given, which keeps it just below a 5.

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.