Skip to main content
Glama

Website check: redirects, headers, SEO, agent readiness

web_check
Read-only

Facts about a URL from a live fetch, never its body: final URL, status and chain after up to 5 validated redirects, response time, content type, server, security headers present/missing (HSTS, CSP, nosniff, framing, Referrer-Policy, Permissions-Policy), title, description, canonical, lang, Open Graph, robots meta, robots.txt rules for GPTBot, ClaudeBot, Google-Extended, CCBot, PerplexityBot, *, llms.txt, agent card, OpenAPI, x402 discovery, 402 terms. DNS via Cloudflare DoH. Price: $0.005 per successful call, paid in USDC with x402 v2; failed calls and calls that match nothing are not charged.

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
urlYeshttp or https URL, or a bare domain (checked as https://). Default ports only; credentials, IP addresses, localhost and private or single-label names are rejected.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior5/5

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

Beyond readOnlyHint/openWorldHint, the description discloses the details an agent actually needs: it never returns the body, redirects are capped at 5 and validated, DNS is resolved via Cloudflare DoH, and — critically — the cost model is spelled out ($0.005 per successful call in USDC via x402 v2, with failures and empty matches free). That pricing/auth disclosure is behavior no annotation carries.

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 definition is front-loaded with the highest-value fact ('never its body') and the remainder is a compressed enumeration where each clause corresponds to a return field. It is dense but nearly waste-free; the pricing sentence is long yet earns its place because cost is decision-relevant. Slightly better segmentation of the fact list would push this higher.

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?

With no output schema, the description carries the full burden of describing what comes back, and it does so exhaustively — status/chain, timing, content type, server, six named security headers, SEO metadata, crawler rules for five named bots plus wildcard, and agent-readiness artifacts. Cost, failure-charging and DNS resolution method round out the operational picture, so nothing an agent needs before calling 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?

There is a single parameter at 100% schema coverage, and the schema itself already documents the http/https-or-bare-domain behavior plus the rejection of credentials, IPs, localhost and private/single-label names. The description correctly does not duplicate that, keeping only the relevant 'never its body' framing. No additional parameter meaning is added, which is acceptable given the schema fully covers it.

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 opens by naming the resource and scope precisely — 'Facts about a URL from a live fetch, never its body' — and then enumerates exactly which facts (final URL, redirect chain, security headers, title/canonical, robots.txt rules, llms.txt, agent card, x402 discovery). That is a specific verb-plus-resource statement an agent can act on. It stops short of 5 because it never names a sibling or states which adjacent tool (e.g. domain_dns, x402_preflight) covers overlapping ground, so the boundary is left to inference.

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 only implied: the enumerated fact set tells the reader this is the tool for auditing a URL's redirects, headers, SEO metadata and agent-readiness artifacts. There is no explicit 'use this when…' clause, no exclusions, and no routing to alternatives despite several siblings (domain_dns, domain_report, x402_preflight) plausibly overlapping. The mention of 'DNS via Cloudflare DoH' arguably increases rather than resolves the domain_dns ambiguity.

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