Skip to main content
Glama

zato: Ethereum & Base Data API (pay-per-call x402)

Check an x402 endpoint

x402_check
Read-only

Check an x402 endpoint: validates the 402 payment challenge (price, network, payTo, Bazaar metadata). Probe a URL (GET, then POST) and report whether it returns a valid x402 402 challenge: version, accepted payments, resource, Bazaar discovery extension and compliance hints. Price: $0.001 USDC per call (x402 v2, Base). Free demo: https://api.zato.org/demo/x402/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": "x402_check"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesPublic http(s) URL

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already establish readOnlyHint and openWorldHint, yet the description adds real behavior: it issues GET then POST requests against the target, and it discloses a per-call cost of $0.001 USDC on x402 v2/Base with a free demo alternative. It omits timeouts, failure behavior for non-x402 endpoints, and whether the POST probe could have side effects on the target.

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 purpose and dense with useful facts (probe method, reported fields, price, demo). There is mild redundancy between 'validates the 402 payment challenge (price, network, payTo, Bazaar metadata)' and the later re-listing of reported fields, but nothing is seriously wasteful.

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?

With no output schema, the description does the work of describing returns: version, accepted payments, resource, Bazaar discovery extension, and compliance hints. Cost and a free demo are disclosed. Remaining gaps are edge-case behavior (unreachable URLs, non-x402 responses) rather than anything blocking a correct call.

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% with a single well-documented URI parameter (format uri, maxLength 2048), so the schema carries the specification. The description adds only how the URL is consumed (GET then POST probes), which is modest added meaning — baseline 3 is appropriate.

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?

States a specific verb and resource — check/validate an x402 402 payment challenge — and enumerates the validated aspects (price, network, payTo, Bazaar metadata). That is far more specific than the sibling names imply for generic probes like web_meta, although it never explicitly contrasts itself with those siblings.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is implied: give it a public URL and it probes it to determine x402 compliance. There is no explicit when-to-use/when-not guidance, no statement about what to do if the URL is unreachable or not x402-enabled, and no comparison to nearby web_* tools; the pricing and demo link add practical context but not selection criteria.

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