Skip to main content
Glama

Site Intelligence

site-intel
Read-only

Get comprehensive domain intelligence: WHOIS, DNS, SSL, tech stack, email security, hosting. Returns, by mode, the registration (WHOIS) data, DNS records with email security, the technology stack, a security grade from A to F, or the subdomains; overview combines registration, DNS, SSL and hosting. Use for technical facts about a domain. For business facts about the company behind it use companies; to find a name you can register use domains. Cost: overview 2 credits, whois 1 credit, dns 1 credit, tech-stack 2 credits, security 2 credits, subdomains 2 credits, charged only when a call succeeds.

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": "site-intel"
  }
}

Input Schema

NameRequiredDescriptionDefault
modeNoIntelligence depth.overview
domainYesDomain to analyze (e.g. stripe.com).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already establish read-only, non-destructive, open-world behavior, and the description goes beyond them by disclosing per-mode credit costs (overview 2, whois 1, etc.) and that charges only apply on success — a genuinely decision-relevant fact for an agent picking a mode. It stops short of describing failure modes (invalid domain, lookup timeouts) or latency, so it is strong but not exhaustive.

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 purpose, then returns-by-mode, then routing, then cost — a sensible order with no filler. The opening data-class list partially overlaps the 'Returns, by mode' sentence, which is the only redundancy.

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 only two parameters and no output schema, the description must carry the return-value burden, and it does so mode by mode while also covering cost and sibling disambiguation. Nothing an agent needs to choose a mode and invoke the tool correctly 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?

Schema coverage is 100%, so the baseline is 3, but the description adds real meaning by mapping each enum value to its output content and noting that overview combines registration, DNS, SSL and hosting. That goes beyond the schema's terse 'Intelligence depth.' for mode.

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 ('Get comprehensive domain intelligence') and enumerates the exact data classes covered (WHOIS, DNS, SSL, tech stack, email security, hosting). It also distinguishes itself from the two nearest siblings, companies and domains, so an agent can route without opening schemas.

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 selection rule: technical facts about a domain here, business facts via 'companies', registerable names via 'domains'. This is a clear when/when-not boundary with named alternatives rather than inferred ones.

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.