Skip to main content
Glama

Confirm a Dagon credit purchase

dagon_confirm_purchase
Idempotent

Report a signed credit purchase to get the configured account credited: pass the fee-sponsored wallet-signed transaction, or the signature of the payment you submitted yourself.

Instructions

Report a dagon_buy_credits payment you signed yourself so the configured account is credited (POST /v1/credits/purchase/confirm). Fee sponsored: pass signed_transaction, the base64 wallet-signed transaction, without submitting it (the payment service adds the fee payer's signature and submits it; resending the same one is safe). Not fee sponsored: submit it yourself and pass its signature.

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": {
      "purchase_id": "<purchase_id>"
    },
    "name": "dagon_confirm_purchase"
  }
}

Input Schema

NameRequiredDescriptionDefault
signatureNoBase58 Solana transaction signature of the payment you submitted (not fee sponsored).
purchase_idYespurchase_id returned by dagon_buy_credits.
signed_transactionNoBase64 wallet-signed transaction of a fee-sponsored purchase, not submitted.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.3/5.0
Behavior5/5

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

Annotations already declare a non-read-only, open-world, idempotent call; the description adds substantive mechanics beyond them: the payment service appends the fee payer's signature and performs submission, and resending the same transaction is safe. It also discloses the required permission boundary implicitly by naming who submits in each mode, which is real operational context an agent cannot get from the hints.

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 purpose and endpoint, then branches cleanly on fee sponsorship. Parenthetical nesting ('(the payment service adds the fee payer's signature and submits it; resending the same one is safe)') is dense, but every clause carries information and nothing is padding.

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?

Covers both invocation modes, the prerequisite purchase_id source, submission responsibility, and idempotency — enough to call it correctly for a 3-parameter tool. With no output schema, it does not say what is returned on success (e.g., credited balance or confirmation id), which is the only meaningful gap.

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 all three parameters are already documented, and the description largely restates signed_transaction's 'base64 wallet-signed, not submitted' semantics. Its one genuine addition is the mode-to-parameter mapping (signed_transaction for sponsored, signature for self-submitted), but this is already implied by the schema field descriptions.

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 (report/confirm), the resource (a dagon_buy_credits payment), the effect (configured account credited), and even the underlying endpoint. It explicitly ties itself to the sibling dagon_buy_credits as the preceding step, so an agent can place it in the workflow without opening a 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?

Gives explicit conditional guidance: 'Fee sponsored: pass signed_transaction...' versus 'Not fee sponsored: submit it yourself and pass its signature,' which is exactly the branch an agent must choose between. It lacks only an explicit negative statement (e.g., do not call this before dagon_buy_credits returns a purchase_id), which is left implicit.

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