Skip to main content
Glama

x402check__trust

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/trust

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__trust"
  }
}

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. Added

TDQS

A4.3/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 the return shape ('Verdict + problem list'), the paid nature of the call, the exact price and currency, and where the payment payload must be placed (params._meta["x402/payment"]). It does not cover failure semantics, whether unpaid or failed calls are billed, or rate limits, which keeps it below 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?

It is dense and front-loaded, leading with purpose, then output shape, then the alternative, then commercial/payment mechanics. The colon-delimited phrasing is slightly run-on but almost every clause carries operational information.

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 one-parameter preflight tool with no output schema, the description covers purpose, return shape, the alternative tool, price and payment mechanics, and even the HTTP transport. Only error/billing edge cases are left unspecified, which is a minor gap at this complexity level.

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% for the single url parameter, so the baseline is 3, but the description adds meaning the schema does not: the payment envelope parameter params._meta["x402/payment"], its currency/network (USDC on Base, eip155:8453), and the per-call cost. That is genuinely useful information absent from structured fields.

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?

The description uses a specific verb ('Preflight') on a specific resource ('an x402 endpoint') and enumerates the exact checks performed: reachability, valid 402 terms, OFAC-screened payTo, and domain age. It also distinguishes itself from the sibling bundle tool by noting that bundle screens company, domain and endpoint together, so an agent can route without opening either schema.

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?

'Preflight an x402 endpoint before you pay it' gives a clear trigger condition, and the bundle sentence implies an alternative when broader company/domain screening is needed. It stops short of an explicit when-not-to-use statement or naming other siblings like screen or address.

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