Skip to main content
Glama

x402check__bundle

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

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

Input Schema

NameRequiredDescriptionDefault
urlYeshttps URL of the x402 endpoint to preflight

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4/5.0
Behavior4/5

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

With no annotations supplied, the description carries the full burden and does most of it: it discloses cost ($0.01 USDC on Base, eip155:8453), the payment mechanism (x402 payment passed in params._meta['x402/payment']), the transport (GET to a specific URL), and the response shape (verdict plus problem list). The remaining gap is failure/edge behavior — whether the fee is charged when the endpoint is unreachable, and any timeout or error semantics — which matters a great deal for a tool that spends money.

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 core value proposition and the preflight trigger are front-loaded in the first clause, and the price, payment channel and transport follow in a compact block. The middle sentence about screening company, domain and endpoint is mildly confusing against a schema that accepts only a URL, but overall there is little waste.

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, no-output-schema tool, the definition supplies what structured fields lack: the checks, the return shape, the cost and the payment mechanics. Completeness is only slightly short because the billing-on-failure question and the mismatch between 'screens company, domain and endpoint' and a URL-only input are left unresolved.

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 documented parameter, so the baseline would be 3. The description earns an extra point by revealing a parameter channel the schema does not mention at all — params._meta['x402/payment'] — which is essential for the agent to actually complete the invocation.

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 names a specific verb and resource ('Preflight an x402 endpoint before you pay it') and enumerates the actual checks performed: reachability, valid 402 terms, OFAC screening of payTo, and domain age, plus the return shape ('Verdict + problem list'). It stops short of a 5 because it never names or contrasts a sibling (e.g. x402check__check or x402check__trust), leaving the agent to infer why this bundle differs from the single-purpose variants.

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 trigger condition is stated plainly and actionably: run it before paying an endpoint, i.e. as a preflight gate. It also frames the scope as covering company, domain and endpoint 'in one call,' which implies preferring this over piecemeal calls. There is no explicit when-not guidance or named alternative for narrower needs.

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