Skip to main content
Glama

Simulate sandbox charge event

sandbox_trigger
Destructive

Simulate a test payment state transition on a sandbox charge and fire its matching webhook without moving real funds. Supports confirmed, partially paid, expired, underpaid, settled and overpaid events.

Instructions

Push a test charge into a payment state (confirmed, partially paid, overpaid, expired, underpaid, settled, settlement failed) without moving funds, and fire the matching webhook. Test environment only.

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": {
      "event": "<event>",
      "chargeId": "<chargeId>"
    },
    "name": "sandbox_trigger"
  }
}

Input Schema

NameRequiredDescriptionDefault
eventYesEvery charge event that represents a payment-progress state transition a sandbox charge can be pushed into — everything except `charge.created` (a charge already exists by the time you have an id to trigger against) and the two escrow-terminal events, which are reached by actually calling `POST /v1/charges/{id}/release` or `POST /v1/charges/{id}/refund` on a test-environment escrow charge (a real Safe transaction on that network's testnet), not this generic trigger.
amountNoUsed with `charge.partially_paid` (amount to simulate as received so far — must be less than the charge amount, defaults to half of it if omitted) and with `charge.overpaid` (amount received — must be greater than the charge amount, defaults to 1.5x it if omitted). Ignored for every other event.
chargeIdYesA Klappay charge id (`ch_` followed by letters and digits).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already flag destructive=true, non-idempotent, and open-world, yet the description adds genuinely new behavioral facts: no funds actually move and a matching webhook is fired as a side effect. That webhook side effect is the key undisclosed-in-annotations behavior an agent needs. It stops short of covering repeat-call behavior or whether repeated triggers are reversible.

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?

A single well-structured sentence, front-loaded with the action and effect, with the test-environment caveat at the end. The enumerated parenthetical of seven states duplicates the enum list and is slightly padded, but it is compact and readable.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a mutating simulation tool with no output schema, the description covers the core effect (state change plus webhook) but says nothing about what the call returns or how to verify the result. An agent can invoke it correctly, but must discover the response shape on its own.

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% and the event/amount descriptions in the schema are far richer than the description's parenthetical state list, so the description adds little meaning beyond the structured fields. The state names in the description merely mirror the enum values. Baseline 3 is appropriate when the schema does the heavy lifting.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

Specific verb ('Push a test charge') plus a concrete resource and enumerated target states, so an agent immediately knows this mutates charge payment status in a sandbox. It does not name sibling alternatives (e.g., charges_create or charges_prepare_refund), so the distinction from those tools must be inferred, but the simulation framing is unambiguous.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

'Test environment only' is a useful usage constraint that rules out production, and the states listed imply when the tool applies. However, there is no explicit guidance on when to prefer this over charges_create or charges_prepare_refund/release, nor prerequisites such as needing an existing `ch_` id in test mode only implicitly via the schema.

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