Skip to main content
Glama

Website Report - tech stack, preview, security grade, domain age

website_report
Read-onlyIdempotent

One call for one website: technologies (CMS, frameworks, analytics, hosting) with versions, title/description/Open Graph image, security headers + SSL grade, and domain age from RDAP. ~2-5 s. Free: 25 calls/day per IP. Paid: $0.01 per call via x402 at https://radarbg.com/x402/website-report.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "domain": "stripe.com"
    },
    "name": "website_report"
  }
}

Input Schema

NameRequiredDescriptionDefault
domainYesWebsite domain or URL, e.g. stripe.com

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Beyond the readOnly/openWorld/idempotent annotations, the description discloses latency (~2-5 s), a free-tier rate limit (25 calls/day per IP), and paid pricing ($0.01 per call via x402 with an endpoint URL) — exactly the operational context annotations cannot convey. It stops short of describing failure behavior for invalid domains or whether results are cached.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two tight sentences: capability and payload first, operational constraints second. No filler, no restating of the title, and the cost/latency facts are packed into a single closing sentence.

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 correctly enumerates returned data categories so an agent knows what to expect, and annotations plus the cost model cover the safety and access profile. The remaining gap is edge-case behavior (invalid or unresolvable domains, partial results when RDAP or SSL lookup fails).

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 description coverage is 100% and the single 'domain' parameter already carries format guidance and an example (stripe.com), so the schema does the heavy lifting. The description adds only that one call maps to one website, which is marginal semantic value over the schema.

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 concrete scope ('One call for one website') and enumerates the exact payload: technologies with versions, title/description/OG image, security headers + SSL grade, and RDAP domain age. That combination distinguishes it from narrower siblings like domain_security_report or web_page_report without needing to name them.

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?

'One call for one website' implies a consolidated single-domain lookup, which is implicit guidance on when this beats a narrower report tool. However, there is no explicit when-to-use, when-not-to-use, or named alternative, so selection between this and the sibling report tools is left to inference.

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