Skip to main content
Glama

Sitesy Website Intelligence

Full website report

website_intelligence
Read-onlyIdempotent

Full website report for one domain: published contact details, tech stack clues, transport security, response headers, DNS records, certificate basics, and hygiene findings ranked by severity. Use this for a one shot overview; use the smaller tools when you need only one of those parts. Costs 0.01 USDC per call. The caller pays per call in USDC on Base through x402: the first call returns the payment requirements, and an x402 aware MCP client signs and retries automatically.

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": {
      "domain": "<domain>"
    },
    "name": "website_intelligence"
  }
}

Input Schema

NameRequiredDescriptionDefault
domainYesA domain name, for example example.com

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, openWorld, non-destructive). The description adds materially beyond them: an explicit per-call price of 0.01 USDC, the Base/x402 payment mechanism, and the two-step first-call-then-retry behavior, which is uncommon and valuable. It does not describe output size or shape, which keeps it from a 5.

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?

Three sentences, front-loaded with the report contents and followed by routing and payment notes; nothing is padded. The contents enumeration is long but each item earns its place by telling the agent what comes back in the absence of an output schema.

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 necessary work of listing the report sections and the severity-ranked findings, so the agent knows what to expect. The payment precondition is also spelled out. Minor gaps remain around response size, latency, and failure behavior, but nothing essential to calling it correctly is missing.

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% and the single `domain` parameter already carries a format example, so the description has little to add. It never mentions the parameter or any constraints such as whether a subdomain or URL is accepted, leaving the baseline 3 appropriate.

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?

Names a specific resource (one domain) and enumerates exactly what the report contains: contact details, tech stack, transport security, response headers, DNS records, certificate basics, and severity-ranked hygiene findings. It also distinguishes itself from the per-part tools, so an agent can tell this apart from dns_lookup or page_metadata without opening a schema.

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

Usage Guidelines5/5

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

Gives an explicit when-to-use rule ("one shot overview") plus a when-not rule ("use the smaller tools when you need only one of those parts"). It also supplies the operational workflow for the paid call (first call returns payment requirements, x402 client signs and retries), which is the guidance an agent needs before invoking.

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