Skip to main content
Glama

x402check__check

Preflight an x402 endpoint before you pay it: reachable, valid 402 terms, payTo OFAC-screened, domain age. Verdict + problem list. Bundle report screens company, domain and endpoint in one call. Price: $0.01 per call in USDC on Base (eip155:8453), paid with x402 in params._meta["x402/payment"]. HTTP: GET https://api.firstmention.uk/s/x402check/check

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

Input Schema

NameRequiredDescriptionDefault
urlYeshttps URL of the x402 endpoint to preflight

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • addedInput schema / properties / url / description
      Added value: +"https URL of the x402 endpoint to preflight"
    • addedInput schema / properties / url / format
      Added value: +"uri"
    • addedInput schema / required
      Added value: +[
      +  "url"
      +]
  2. Changed3 schema fields changed
    • removedInput schema / properties / url / description
      Removed value: -"Public HTTPS URL of the x402 endpoint to preflight"
    • removedInput schema / properties / url / format
      Removed value: -"uri"
    • removedInput schema / required
      Removed value: -[
      -  "url"
      -]
  3. Changed3 schema fields changed
    • addedInput schema / properties / url / description
      Added value: +"Public HTTPS URL of the x402 endpoint to preflight"
    • addedInput schema / properties / url / format
      Added value: +"uri"
    • addedInput schema / required
      Added value: +[
      +  "url"
      +]
  4. Changed3 schema fields changed
    • removedInput schema / properties / url / description
      Removed value: -"https URL of the x402 endpoint to preflight"
    • removedInput schema / properties / url / format
      Removed value: -"uri"
    • removedInput schema / required
      Removed value: -[
      -  "url"
      -]
  5. Changed3 schema fields changed
    • addedInput schema / properties / url / description
      Added value: +"https URL of the x402 endpoint to preflight"
    • addedInput schema / properties / url / format
      Added value: +"uri"
    • addedInput schema / required
      Added value: +[
      +  "url"
      +]
  6. Changed5 schema fields changed
    • removedInput schema / properties / address
      Removed value: -{
      -  "description": "0x eth address for /balance or /nonce",
      -  "type": "string"
      -}
    • removedInput schema / properties / chain
      Removed value: -{
      -  "description": "which chain to read, default base",
      -  "enum": [
      -    "base",
      -    "eth"
      -  ],
      -  "type": "string"
      -}
    • removedInput schema / properties / hash
      Removed value: -{
      -  "description": "0x transaction hash for /tx",
      -  "type": "string"
      -}
    • removedInput schema / properties / token
      Removed value: -{
      -  "description": "ERC20 contract 0x address for /erc20",
      -  "type": "string"
      -}
    • removedInput schema / properties / url / description
      Removed value: -"seller URL for /check"
  7. Changed7 schema fields changed
    • addedInput schema / properties / address
      Added value: +{
      +  "description": "0x eth address for /balance or /nonce",
      +  "type": "string"
      +}
    • addedInput schema / properties / chain
      Added value: +{
      +  "description": "which chain to read, default base",
      +  "enum": [
      +    "base",
      +    "eth"
      +  ],
      +  "type": "string"
      +}
    • addedInput schema / properties / hash
      Added value: +{
      +  "description": "0x transaction hash for /tx",
      +  "type": "string"
      +}
    • addedInput schema / properties / token
      Added value: +{
      +  "description": "ERC20 contract 0x address for /erc20",
      +  "type": "string"
      +}
    • changedInput schema / properties / url / description
      Previous value: -"Full HTTPS URL of the x402 endpoint to inspect."New value: +"seller URL for /check"
    • removedInput schema / properties / url / format
      Removed value: -"uri"
    • removedInput schema / required
      Removed value: -[
      -  "url"
      -]
  8. First observed

TDQS

A4.3/5.0
Behavior5/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 so: it discloses the cost ($0.01 USDC on Base eip155:8453), the payment channel (params._meta["x402/payment"]), and the transport (HTTP GET to a specific URL). It also clarifies this is a read-only preflight returning a verdict plus problem list, which is the key behavioral profile an agent needs before invoking a paid tool.

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-loaded with the purpose and checks, then cost and transport. The colon-separated list is dense but readable. Minor cost for cramming pricing, payment path and endpoint URL into a single paragraph, though each element is actionable.

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, and the description summarizes the return as 'Verdict + problem list', which is thin but sufficient for a one-parameter preflight. Payment mechanics and endpoint are covered; only the verdict value space is left implicit.

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 url parameter is fully documented, so baseline is 3. The description adds value by revealing a payment envelope (params._meta["x402/payment"]) that does not appear in the schema, but it does not describe the url beyond 'x402 endpoint'.

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?

States a specific verb and resource ('Preflight an x402 endpoint') and enumerates exactly what is checked: reachability, 402 terms validity, OFAC screening of payTo, domain age. It also names the output ('Verdict + problem list'), so an agent knows what comes back and can distinguish this from sibling checks.

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?

'before you pay it' gives a clear triggering condition for the tool. It also routes the agent toward the bundle alternative by noting that the bundle report screens company, domain and endpoint in one call, though it does not spell out an explicit when-not-to-use rule.

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