Skip to main content
Glama

X420 agent services

x420_http_endpoint-check

Read-onlyIdempotent

HTTP endpoint check: One GET or HEAD to a public URL: status, latency, redirects (each hop re-checked), final URL and the security/caching headers. Private and internal addresses are refused. Not professional, legal, insurance, engineering, medical, financial or tax advice. Price: $0.02 USDC per call (x402 on Base). This hosted tool does NOT pay and does NOT return the deliverable: it validates the input and returns payment instructions (pay_to, network, price and the x402 URL to pay at). GET the url; read PAYMENT-REQUIRED from the 402; retry with PAYMENT-SIGNATURE (x402 v2). Or run the local x420-mcp server with your own wallet key to pay automatically. Deliverable once paid: JSON: status, ok, latency_ms, redirects, final_url, https, headers{}.

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": "x420_http_endpoint-check"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYespublic http(s) URL
methodNoget (default) or head

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior5/5

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

Beyond the annotations (readOnly, openWorld, idempotent, non-destructive), it discloses the critical behavior that this hosted instance does not pay and does not return the deliverable, the exact payment mechanics, the price and network, and the refusal of private/internal addresses. The 402 handshake detail is exactly the kind of non-obvious trait an agent needs before calling.

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 capability and the payment caveat are front-loaded, which is the right ordering for a tool that fails without payment. It is dense but well ordered; the boilerplate disclaimer ('Not professional, legal, insurance...advice') and some payment prose could be trimmed without losing agent-relevant information.

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 paid, redirect-following HTTP check with no output schema, the description covers the input constraints, the payment handshake, the local-server alternative, and the shape of the deliverable JSON (status, ok, latency_ms, redirects, final_url, https, headers). Nothing an agent needs to invoke it successfully is missing.

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%, so the schema already documents both parameters, which sets a baseline of 3. The description adds real constraint semantics not present in the schema: only public http(s) targets, private and internal addresses refused, and one request only (not a crawl).

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 concrete verb and resource ('One GET or HEAD to a public URL') and enumerates what is returned: status, latency, redirects, final URL and security/caching headers. That scope (a single request) implicitly separates it from broader siblings such as x420_sitescan_check, but no sibling is named explicitly, so the differentiation is inferential rather than stated.

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?

It gives an explicit call sequence: GET the url, read PAYMENT-REQUIRED from the 402, retry with PAYMENT-SIGNATURE, and offers the alternative of running the local x420-mcp server with your own wallet key. It does not state when to prefer this over sibling checks like sitescan_check or validate_email-url-phone, so alternatives are covered only for the payment path.

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