Skip to main content
Glama

Donate USDC to Immersive Commons via x402 (public)

ic_donate

Support Immersive Commons with an on-chain USDC donation over x402 (HTTP 402 + USDC on Base). No auth required. Returns the donation tiers, the receiving wallet (payTo), the asset + network, and the donate URL. MCP can't run the in-band 402 handshake itself, so to donate: POST https://www.immersivecommons.com/api/x402/donate with an x402 X-PAYMENT header (sign an EIP-3009 USDC authorization for one of the tier amounts to payTo on the given network); the first call with no X-PAYMENT returns a 402 listing every tier in accepts[]. Optional donor { name, message } can be sent in the JSON body and appear on the public donor wall at /donate. Args: { tier?: string (a tier label, case-insensitive — narrows tiers[] to that single tier and adds selected_tier with the exact atomic USDC amount to sign; an unknown label returns error_kind:"validation" naming the valid labels) }.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "ic_donate"
  }
}

Input Schema

NameRequiredDescriptionDefault
tierNoA tier label, case-insensitive. Narrows tiers[] to that tier and adds selected_tier with the exact USDC amount to sign.

Output Schema

NameRequiredDescriptionDefault
okNotrue when the call did what it was asked; false with `error` and `error_kind` when it did not
textNoThe tool's reply when it returns plain text instead of JSON
errorNoWhy the call failed, in a sentence a person can act on. Present only when ok is false.
resultNoThe tool's value when it returns a list or a single value instead of an object
error_kindNoMachine-readable failure class: no_token, missing_scope, forbidden, not_found, invalid_input, rate_limited or transient

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "$schema": "http://json-schema.org/draft-07/schema#",
      +  "additionalProperties": {},
      +  "description": "The tool's JSON result. Every field the tool's description names is present at the top level; ok, error and error_kind follow the shared envelope.",
      +  "properties": {
      +    "error": {
      +      "description": "Why the call failed, in a sentence a person can act on. Present only when ok is false."
      +    },
      +    "error_kind": {
      +      "description": "Machine-readable failure class: no_token, missing_scope, forbidden, not_found, invalid_input, rate_limited or transient"
      +    },
      +    "ok": {
      +      "description": "true when the call did what it was asked; false with `error` and `error_kind` when it did not"
      +    },
      +    "result": {
      +      "description": "The tool's value when it returns a list or a single value instead of an object"
      +    },
      +    "text": {
      +      "description": "The tool's reply when it returns plain text instead of JSON"
      +    }
      +  },
      +  "type": "object"
      +}
  2. Changed1 schema field changed
    • addedInput schema / properties / tier / description
      Added value: +"A tier label, case-insensitive. Narrows tiers[] to that tier and adds selected_tier with the exact USDC amount to sign."
  3. Changed1 schema field changed
    • removedInput schema / properties / tier / description
      Removed value: -"A tier label, case-insensitive. Narrows tiers[] to that tier and adds selected_tier with the exact USDC amount to sign."
  4. Changed1 schema field changed
    • addedInput schema / properties / tier / description
      Added value: +"A tier label, case-insensitive. Narrows tiers[] to that tier and adds selected_tier with the exact USDC amount to sign."
  5. Changed1 schema field changed
    • addedInput schema / properties / tier
      Added value: +{
      +  "maxLength": 64,
      +  "minLength": 1,
      +  "type": "string"
      +}
  6. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations only mark it as non-read-only and non-destructive; the description adds the material facts beyond that — no auth required, an actual on-chain USDC spend, the client-side signing step MCP cannot perform in-band, and that an optional donor name/message becomes publicly visible on the donor wall. It stops short of stating that a signed authorization is final/irreversible, which is the one behavioral gap for a payment tool.

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, then mechanics, then args — a sensible ordering. It is dense and somewhat run-on with nested parentheses, and the closing 'Args:' sentence largely restates the schema, but no sentence is wasted given the payment workflow it must convey.

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?

With an output schema present, return values need only light coverage, and the description still summarizes tiers/payTo/asset/network/donate URL. For a payment tool with a manual 402 handshake, it is nearly complete; absence of confirmation/idempotency behavior after a successful X-PAYMENT POST is the remaining gap.

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; the description earns above that by explaining the side effects of the parameter (narrows tiers[] to a single tier and appends selected_tier with the exact atomic amount to sign) and the failure mode (unknown label returns error_kind:"validation" naming valid labels).

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?

Opens with a specific verb+resource+mechanism: 'Support Immersive Commons with an on-chain USDC donation over x402 (HTTP 402 + USDC on Base).' It is unambiguously a payment tool, distinguishable from read-only siblings like ic_donations_total, and it names the network and asset up front.

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 clear procedural guidance for when and how to use it: call first without X-PAYMENT to receive the 402 tier list from accepts[], then POST with an X-PAYMENT header containing an EIP-3009 authorization. It does not name confused alternatives (e.g., clarifying versus ic_donations_total), but the operational context is explicit.

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.