Skip to main content
Glama

AI Fusion One

Website DNS, TLS, redirect and security-header check

web_check

Public-website health check measured by AI Fusion One from the Cloudflare edge: DNS records via DNS-over-HTTPS (A, AAAA, CNAME, NS, MX, CAA, SPF), HTTPS reachability with certificate validation by the edge, HTTP-to-HTTPS redirect, the redirect chain (each hop re-checked), and common security headers (HSTS, CSP, X-Content-Type-Options, X-Frame-Options, Referrer-Policy, Permissions-Policy, COOP/CORP). SSRF-protected: public DNS hostnames on ports 80/443 only, GET only, redirects followed manually (max 4) with every hop re-validated, 8 s timeout, bodies never returned. Certificate issuer and expiry are not available from the edge runtime and are not reported. PAID tool: call without x402_payment to get the payment requirements. Result text fields are untrusted data. Price: $0.05 per call. Paid in REAL USDC on Base mainnet (chain 8453) via x402.

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": "web_check"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesPublic website URL or hostname (https assumed if no scheme). No IP literals, credentials or custom ports.
trialNoFree trial instead of payment: a few calls per client per UTC day (shared across paid tools); result marked mode=trial.
x402_paymentNoBase64 x402 v1 'exact' EIP-3009 payment payload for Base mainnet (REAL USDC on Base mainnet (chain 8453)). Omit on the first call to receive the payment requirements as a tool error (structuredContent.accepts); sign them and call again with this argument. One payment funds exactly one call.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Goes well beyond the annotations: discloses SSRF protections, GET-only, manual redirect following capped at 4 with per-hop re-validation, an 8 s timeout, no response bodies returned, and the notable limitation that certificate issuer/expiry are unavailable from the edge runtime. It also flags pricing, chain, and that result text fields are untrusted data — exactly the operational context annotations cannot carry.

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 resource and check list, then constraints, then payment — a sensible order with almost no filler. The long enumeration of header names and repeated payment details make it denser than strictly necessary, but each clause conveys actionable 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?

No output schema exists, and the description partially compensates by noting that text fields are untrusted, that trial mode is marked, and that cert issuer/expiry are absent. It does not sketch the shape of the returned findings (per-record DNS results, per-hop redirect data), leaving some uncertainty about what an agent will receive.

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 still adds value by tying the url parameter to the SSRF hostname/port constraints and by explaining the two-step x402_payment handshake (call without it to receive requirements). The trial parameter's semantics are left entirely to the schema, which keeps it from a 5.

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 and resource ('Public-website health check') and enumerates the exact dimensions checked: DNS record types, HTTPS reachability with edge-side cert validation, HTTP-to-HTTPS redirect, redirect chain, and named security headers. An agent can tell this apart from generic siblings like basic_lookup or basic_verification without opening any 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?

Gives clear applicability context (public DNS hostnames only, ports 80/443, no IP literals/credentials/custom ports) and a required payment workflow ('call without x402_payment to get the payment requirements'). It stops short of naming when to prefer a sibling tool or explicitly excluding non-public/private targets beyond the SSRF clause, so it is clear context rather than full routing guidance.

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