Skip to main content
Glama

Pay safe batch

pay_safe_batch

Pre-send batch check for up to 10 payees ($0.03): returns one signed PaySafe verdict per recipient (poisoning lookalike, USDC blacklist, OFAC). Not a permission to pay. $0.03 per call over x402 (USDC on Arc, Base or Solana, or XNT on X1). Call once without payment for the terms, sign them with your own wallet, call again with payment.

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": {
      "items": "<items>"
    },
    "name": "pay_safe_batch"
  }
}

Input Schema

NameRequiredDescriptionDefault
chainNodefault chain (arc|base)
itemsYesJSON array of objects or strings, e.g. [{"payee":"0x3600000000000000000000000000000000000000","chain":"arc"}]
payerNooptional payer 0x address
windowNoduplicate-check window seconds
paymentNoa signed x402 payment (the base64 payload you would put in PAYMENT-SIGNATURE). Pass it and the purchase completes inside this tool call.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does well: it discloses pricing ($0.03 per call), accepted payment rails (x402 USDC on Arc/Base/Solana, XNT on X1), the two-step signature handshake, and the important limitation 'Not a permission to pay.' It stops short of describing failure modes or what happens if payment is invalid or the batch exceeds 10.

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?

Dense and front-loaded: purpose and output first, caveat next, pricing and invocation flow last. The $0.03 figure appears twice, which is minor redundancy, but no sentence is filler.

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?

No output schema exists, so the description must describe returns, and it does: one signed verdict per recipient across three check types. The payment flow, cost, and rails are all covered. Gaps are edge cases (over-limit batches, payment failure handling), which are minor for a 1-required-param tool.

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 baseline is 3, but the description adds real meaning for the `payment` parameter: it is a signed x402 payload and passing it completes the purchase inside the call, which the schema only hints at. The `items` cap of 10 payees and the per-recipient output are also stated, adding semantics beyond the raw schema.

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: a pre-send batch check of up to 10 payees that returns one signed PaySafe verdict per recipient, with the three check categories named (lookalike, USDC blacklist, OFAC). The 'batch' framing distinguishes it from a single-payee check, though no sibling is named explicitly.

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?

Clear usage context: use it before sending funds, and the exact invocation protocol is given (call once without `payment` for terms, sign, call again with `payment`). What is missing is an explicit alternative for single payees or a statement of the limit behavior beyond 10 items.

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