Skip to main content
Glama

SCRIPTMASTERLABS — GatePay

GatePay Execute Payout

gatepay_route
Destructive

Execute a payout through the existing GatePay route logic (same caps, allowlist, ledger and Arc settlement path as POST /v1/route). Executes ONLY when the MCP HTTP request carries the X-GatePay-Route-Key header; a missing or wrong key is a hard refusal before any policy, ledger or settlement step runs.

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": {
      "amount": "<amount>",
      "destination": "<destination>"
    },
    "name": "gatepay_route"
  }
}

Input Schema

NameRequiredDescriptionDefault
memoNoOptional memo recorded with the request payload.
amountYesAmount in USDC.
destinationYesDestination wallet address on Arc.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Adds real context beyond the annotations: it names the enforcement layers (caps, allowlist, ledger, Arc settlement) and specifies that an auth failure short-circuits before any policy, ledger, or settlement step. What it omits is duplicate-payout/retry behavior, which the annotations already flag via idempotentHint=false, so the gap is limited.

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?

Two sentences, both front-loaded with the action first and the auth gate second. No filler, no restatement of the title, and the parenthetical enumerates the concrete backend stages in a compact form.

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 destructive, non-idempotent, open-world money-movement tool, the description covers the critical unknowns: what backend path executes and what the auth gate blocks. It lacks any indication of a success response shape (no output schema exists) and gives no retry/duplicate guidance for a non-idempotent payout.

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 amount (USDC, >0), destination (Arc address), and memo are fully documented structurally; the description adds no format, precision, or bounds detail beyond referencing caps/allowlist. Baseline 3 is appropriate.

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?

States a specific verb and resource ('Execute a payout') and anchors it to known backend semantics ('same caps, allowlist, ledger and Arc settlement path as POST /v1/route'). The action is unmistakably distinct from the policy/quote/status siblings, though no sibling is named for contrast.

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?

Provides a hard precondition (X-GatePay-Route-Key header must be present) which effectively tells the agent when this will run, but never states the intended sequencing versus gatepay_policy or gatepay_quote, nor any when-not-to-use case.

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.

Resources