Skip to main content
Glama

PayStage — x402 payment safety and spend policy

request_testnet_funds

test funds. Call this when you need Base Sepolia USDC to exercise the paid path end to end — one drip of 0.5 USDC per address per 24 hours, and the refusal tells you when it resets rather than just failing. Reads a public faucet: no key needed, no account, and it can only ever send testnet USDC. Use a throwaway address for anything automated; the cap is per address, so a script that generates a new address per call is not clever, it is why faucets get closed.

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": {
      "address": "<address>"
    },
    "name": "request_testnet_funds"
  }
}

Input Schema

NameRequiredDescriptionDefault
addressYes
faucetUrlNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior5/5

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

Goes well beyond the annotations: it discloses the exact quota (0.5 USDC per address per 24h), that a refusal returns reset timing rather than a bare error, that no key or account is required, that it reads a public faucet, and that it can only ever emit testnet USDC. This is exactly the safety/limits context the annotations (readOnlyHint=false, openWorldHint=true, destructiveHint=false) leave open.

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?

Front-loads the trigger and quota, then layers safety and a pointed abuse warning; the closing remark is stylized but carries real guidance about per-address caps. The opening fragment "test funds." contributes little that the following sentence does not say better.

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 two-parameter tool with no output schema, the description covers the important unknowns: quota, reset behavior on refusal, zero auth, and testnet-only scope. The gaps are the unexplained faucetUrl parameter and any hint about what a successful call returns (tx hash vs. confirmation).

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 description coverage is 0%, so the description must carry the parameter meaning. It clarifies that the cap is per address and that the address should be throwaway, implying the address is the recipient identifier, but it never explains what faucetUrl is for or whether it is optional — the second parameter remains a guess.

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?

"test funds" is thin on its own, but the next clause pins it precisely: retrieve Base Sepolia USDC to exercise the paid path end to end. No sibling in the list (decode_payment_required, evaluate_*, verify_receipt) does anything similar, and the description makes the faucet/network explicit so an agent cannot confuse it with the evaluation tools.

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 a concrete trigger — "call this when you need Base Sepolia USDC to exercise the paid path end to end" — plus an implicit when-not via the warning against per-call address generation for automation. It lacks a named alternative (e.g., what to do if you need more than 0.5 USDC), so it stops short of explicit routing.

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.