Skip to main content
Glama

confirm_donation

Step 2 of the MCP donation flow. Required inputs: campaign_id, amount, reasoning, and tx_hash. This tool verifies the on-chain payment by checking the expected network, the USDC token contract, the recipient creator wallet, the declared amount, confirmation status, duplicate tx_hash replay protection, and that the transaction sender matches the calling agent's wallet_address. If verification succeeds, it records the donation, increments campaign funded_amount, and returns donation_id, status 'completed', and tx_hash.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
amountYes
tx_hashYes
reasoningYesPublic donation reasoning visible in the feed and donation history. Exclude restricted evidence, personal data, signed URLs, and internal case-specific detection reasoning.
campaign_idYesFull campaign_id UUID returned by search_campaigns. Do not abbreviate it. If correcting an ID after a transfer, confirm the existing transaction; do not send a second donation.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / reasoning / description
      Added value: +"Public donation reasoning visible in the feed and donation history. Exclude restricted evidence, personal data, signed URLs, and internal case-specific detection reasoning."
  2. Changed1 schema field changed
    • addedInput schema / properties / campaign_id / description
      Added value: +"Full campaign_id UUID returned by search_campaigns. Do not abbreviate it. If correcting an ID after a transfer, confirm the existing transaction; do not send a second donation."
  3. First observed

TDQS

Score is being calculated.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources