Skip to main content
Glama

x420_http_endpoint-check

Check a public HTTP endpoint with one GET or HEAD request to return status, latency, redirects, final URL, and security/caching headers; private and internal addresses are refused.

Instructions

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. PAID: $0.02 USDC per call, settled on Base via x402 from the wallet in X420_MCP_WALLET_PRIVATE_KEY (real money). Returns: JSON: status, ok, latency_ms, redirects, final_url, https, headers{} - the deliverable plus X420's signed receipt and the settlement transaction. Example input: {"url":"https://example.com/"}.

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 observedv1.0.2

TDQS

A4.1/5.0
Behavior4/5

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

Adds substantial behavior beyond the annotations: redirects are re-checked at each hop, SSRF-style blocking of private targets, and — most importantly — that each call costs $0.02 USDC settled on Base via x402 from X420_MCP_WALLET_PRIVATE_KEY (real money). It also discloses the signed receipt and settlement transaction in the response. It does not contradict the annotations, though readOnlyHint=false is never explained (the non-read-only nature is implied only by the payment).

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 operation and its outputs, then constraints, then price, then return shape, then example — a sensible order. The long colon-chained single paragraph and the boilerplate 'not professional, legal, insurance… advice' sentence add bulk, but the disclaimer is arguably required for a paid advisory-adjacent service.

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 carries the return-value burden and does it well: it names status, ok, latency_ms, redirects, final_url, https, headers{}, plus the receipt and settlement tx. Missing only failure/timeout/retry semantics and what happens when settlement fails, which an agent paying per call would want.

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 baseline is 3; the description goes slightly further by restating that a single request is made, that GET is the default and HEAD is the alternative, and by giving a concrete example payload. It adds format guidance (public http(s) URL only) without duplicating the schema verbatim.

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+resource ('HTTP endpoint check: One GET or HEAD to a public URL') and enumerates exactly what is returned: status, latency, redirects, final URL, security/caching headers. It reads distinctly from URL-page siblings like x420_sitescan_check or x420_tls_certificate because it scopes to a single request/response.

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?

Implies usage ('one GET or HEAD to a public URL') and states a hard exclusion (private and internal addresses refused), but never names when to pick this over x420_sitescan_check, x420_sitescan_basic, or x420_tls_certificate. An agent must infer the split itself.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.