Skip to main content
Glama

Pay safe credits

pay_safe_credits

Buy 100 pre-paid wallet-check call credits ($0.20) for repeated PaySafe screening. $0.20 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

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": "pay_safe_credits"
  }
}

Input Schema

NameRequiredDescriptionDefault
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

A3.9/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 cost per call, the x402 payment rail, accepted assets and chains (USDC on Arc/Base/Solana, XNT on X1), and the handshake requirement. It omits failure handling, credit expiry, and what the tool returns, which keeps it from a 5.

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?

Three front-loaded sentences: what you get, what it costs and how to pay, then the call sequence. Slightly muddled by stating $0.20 twice (once parenthetically beside the 100-credit bundle, once as per-call price), which briefly reads as though the bundle costs $0.20.

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 single-parameter purchase tool with no output schema, the description covers price, payment rail, and the required call sequence well. It could state what a successful call returns (credits granted, balance) but nothing critical to invoking it correctly is missing.

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 single `payment` parameter is already documented as a signed x402 payload. The description adds workflow meaning — that omitting it yields terms and that passing it completes the purchase in-call — but the schema alone would nearly suffice, so the baseline 3 applies.

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: buying 100 pre-paid wallet-check credits for repeated PaySafe screening, with the price. The word 'repeated' implicitly distinguishes it from the single-call pay_safe sibling, but no alternative is named outright, so the differentiation is inferred rather than declared.

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 an explicit two-step invocation recipe: call once without `payment` to receive terms, sign with your own wallet, then call again with `payment`. That is concrete when-to-do-what guidance, though it does not say when to prefer this over pay_safe or pay_safe_batch.

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