Skip to main content
Glama

SoapBox Faith

by io.github.alansafahi
OverviewDiscussionsAdmin

give_to_church

DestructiveIdempotent

Make a one-time donation to a church ON BEHALF OF A USER, within the spending caps they pre-authorized. Requires the user's consent_token with the 'giving:write' scope (bound to this agent) and a card they saved in the SoapBox app. The gift goes straight to the church (passthrough — SoapBox takes no cut). Rejected if the amount exceeds the per-gift or monthly cap. Pass a stable idempotency_key to avoid double-charging on retries. Amounts are in the smallest currency unit (cents). This moves the user's money: confirm the church and amount with the user before every call. The user is notified of every gift.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
noteNoOptional short note to the church accompanying the gift.
currencyNoOptional ISO 4217 currency code (lowercase). Must be the church's own currency; omit it to use that. AI-agent gifts are available in USD, CAD, GBP, EUR, AUD and NZD.
amount_centsYesGift amount in the smallest currency unit (cents), at least 100. Must be within the user's per-gift and monthly caps or the call is rejected.
community_idYesThe recipient church's SoapBox community id (e.g. the soapbox_community_id from find_churches).
consent_tokenYesOpaque SoapBox consent token with the 'giving:write' scope, carrying the user's pre-authorized per-gift and monthly caps. Generated by the user in the SoapBox app (Settings › AI Agents). The first agent key to use a token is bound to it; a token no agent uses within 24 hours of being created stops working.
idempotency_keyNoA stable, caller-generated key so retries don't double-charge. Reuse the same key when retrying the same intended gift.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changed
    • changedInput schema / properties / amount_cents / description
      Previous value: -"Gift amount in the smallest currency unit (cents). Must be within the user's per-gift and monthly caps or the call is rejected."New value: +"Gift amount in the smallest currency unit (cents), at least 100. Must be within the user's per-gift and monthly caps or the call is rejected."
    • changedInput schema / properties / amount_cents / minimum
      Previous value: -1New value: +100
    • changedInput schema / properties / consent_token / description
      Previous value: -"Opaque SoapBox consent token with the 'giving:write' scope, bound to your agent key and carrying the user's pre-authorized per-gift and monthly caps. Generated by the user in the SoapBox app."New value: +"Opaque SoapBox consent token with the 'giving:write' scope, carrying the user's pre-authorized per-gift and monthly caps. Generated by the user in the SoapBox app (Settings › AI Agents). The first agent key to use a token is bound to it; a token no agent uses within 24 hours of being created stops working."
    • changedInput schema / properties / consent_token / examples
      Previous value: -[
-  "sbxgv_9f3a2b7c4d5e6f7a…"
-]New value: +[
+  "sbxc_9f3a2b7c4d5e6f7a…"
+]
    • changedInput schema / properties / currency / description
      Previous value: -"Optional ISO 4217 currency code (lowercase). Defaults to the church's own currency."New value: +"Optional ISO 4217 currency code (lowercase). Must be the church's own currency; omit it to use that. AI-agent gifts are available in USD, CAD, GBP, EUR, AUD and NZD."
    • changedInput schema / properties / currency / examples
      Previous value: -[
-  "usd",
-  "ugx"
-]New value: +[
+  "usd",
+  "cad"
+]
  2. Changed16 schema fields changed
    • changedInput schema / properties / amount_cents / description
      Previous value: -"Gift amount in cents (e.g. 2500 = $25). Must be within the user's caps."New value: +"Gift amount in the smallest currency unit (cents). Must be within the user's per-gift and monthly caps or the call is rejected."
    • addedInput schema / properties / amount_cents / examples
      Added value: +[
+  2500
+]
    • addedInput schema / properties / amount_cents / minimum
      Added value: +1
    • changedInput schema / properties / community_id / description
      Previous value: -"The church's SoapBox community id (e.g. from find_churches' soapbox_community_id)."New value: +"The recipient church's SoapBox community id (e.g. the soapbox_community_id from find_churches)."
    • addedInput schema / properties / community_id / examples
      Added value: +[
+  "b3095717-5cc0-4213-8964-a01a5ee6b250"
+]
    • addedInput schema / properties / community_id / format
      Added value: +"uuid"
    • changedInput schema / properties / consent_token / description
      Previous value: -"The user's SoapBox consent token (scope giving:write, bound to this agent)."New value: +"Opaque SoapBox consent token with the 'giving:write' scope, bound to your agent key and carrying the user's pre-authorized per-gift and monthly caps. Generated by the user in the SoapBox app."
    • addedInput schema / properties / consent_token / examples
      Added value: +[
+  "sbxgv_9f3a2b7c4d5e6f7a…"
+]
    • addedInput schema / properties / consent_token / minLength
      Added value: +16
    • changedInput schema / properties / currency / description
      Previous value: -"Optional ISO currency (defaults to the church's currency)."New value: +"Optional ISO 4217 currency code (lowercase). Defaults to the church's own currency."
    • addedInput schema / properties / currency / examples
      Added value: +[
+  "usd",
+  "ugx"
+]
    • addedInput schema / properties / currency / pattern
      Added value: +"^[a-z]{3}$"
    • changedInput schema / properties / idempotency_key / description
      Previous value: -"Stable key to make retries safe (no double-charge)."New value: +"A stable, caller-generated key so retries don't double-charge. Reuse the same key when retrying the same intended gift."
    • addedInput schema / properties / idempotency_key / examples
      Added value: +[
+  "gift-2026-07-20-abc123"
+]
    • changedInput schema / properties / note / description
      Previous value: -"Optional note to the church."New value: +"Optional short note to the church accompanying the gift."
    • addedInput schema / properties / note / maxLength
      Added value: +280
  3. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Beyond the annotations (readOnlyHint=false, destructiveHint=true, idempotentHint=true), the description discloses the passthrough mechanism ('SoapBox takes no cut'), rejection on cap violations, the need for a stable idempotency_key, the mandatory user confirmation, and user notification. These behavioral specifics are not inferable from annotations and substantially aid correct invocation.

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?

The description is front-loaded with the core action, then layers prerequisites, rejection conditions, idempotency, and safety guidance in a logical order. Every sentence carries practical, non-redundant information; no filler, no repetition of annotation values. Its length is justified by the tool's complexity.

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?

For a money-moving tool with no output schema, the description covers prerequisites (token, card), failure modes (caps), idempotency, user-confirmation duty, and notification. It does not specify the response/return payload or what happens when a saved card is missing, but these are minor given the schema and annotations cover the main operational concerns.

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 coverage is 100%, so the baseline is 3. The description mostly repeats schema facts, e.g., 'Amounts are in the smallest currency unit (cents)' and 'Pass a stable idempotency_key to avoid double-charging on retries' mirror the parameter descriptions exactly. It adds no new parameter-level insight beyond what the schema already communicates.

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 starts with a specific verb-resource pair ('Make a one-time donation to a church') and adds the crucial 'ON BEHALF OF A USER' scope, which distinguishes it from generic payment tools. It also mentions the spending-cap constraint and the giving:write consent scope, making it unmistakable among siblings like purchase_sermon or pay_with_x402.

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?

The description gives clear preconditions: a consent_token with 'giving:write', pre-authorized caps, and a saved card. It also instructs the agent to confirm with the user before calling. However, it never explicitly names alternatives or states 'use this for giving, not purchasing', so it stops short of the explicit routing in the strongest examples.

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

All SoapBox Faith toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources