Skip to main content
Glama

MoneyTools payment-safety suite

Pre-check an x402 payment

x402_precheck
Read-onlyIdempotent

Before paying an x402 endpoint: fetch it, validate its HTTP 402 payment requirements (scheme, network, payTo, amount, asset) and screen payTo against the OFAC SDN crypto-address list. Returns verdict ok|warn|block|not_402. Free to try: 20 MCP calls/day per client, no API key or wallet needed (beyond that: prepaid credits via header X-API-Key, see server instructions).

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": {
      "url": "<url>"
    },
    "name": "x402_precheck"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesx402 endpoint you plan to pay
methodNoHTTP method the endpoint expects; default GET

Output Schema

NameRequiredDescriptionDefault
optionsYes
reasonsYes
summaryNo
verdictYes
warningsYes
riskScoreNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior5/5

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

The annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, yet the description still adds materially: it discloses the free-tier rate limit (20 MCP calls/day per client), how to exceed that limit (prepaid credits via the X-API-Key header), and that no wallet or API key is needed for the free tier. That is exactly the authentication and quota context that annotations do not carry, and nothing in it conflicts with the annotation set.

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?

The usage trigger is correctly front-loaded, and the rate-limit and auth aside is compactly parenthesized rather than given its own paragraph. The single long opening sentence packs in a lot of clauses but every clause carries information, so the only cost is mild density.

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

Completeness5/5

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

For a two-parameter read-only check with an output schema, this covers everything an agent needs: when to call it, which fields of the 402 response get validated, the possible verdicts (ok|warn|block|not_402), the cost model, and the credential path for heavy use. Nothing essential to invoking it correctly is left to inference.

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 100%, so the baseline is 3; both parameters are already documented in the schema, including the GET default and the enum. The description's list of validated fields (scheme, network, payTo, amount, asset) describes what is inspected in the response rather than what url or method mean, so it adds no parameter-level meaning beyond the 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?

The description opens with a specific verb and resource: fetch the endpoint, validate its HTTP 402 payment requirements (scheme, network, payTo, amount, asset), and screen payTo against the OFAC SDN list. That is enough for an agent to distinguish it from generic tools, but it never differentiates this tool from its close siblings x402_validate or x402_verify_settlement, so it has no explicit sibling-differentiation credit.

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?

The phrase 'Before paying an x402 endpoint' gives an unambiguous temporal trigger for use, which is more than most definitions offer. However, the description names no alternatives and no exclusions, leaving it silent on when to pick x402_validate or x402_verify_settlement instead, so it falls short of a 5.

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