Skip to main content
Glama

Domain health check (DNS, email auth, TLS, HTTP, crawlers)

check_domain_health
Read-onlyIdempotent

Audit a domain: DNS records, email authentication (SPF, DKIM, DMARC), TLS certificate, HTTP behavior and AI/search crawler rules in robots.txt. Returns findings per check. Up to 3 domains per call.

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

Input Schema

NameRequiredDescriptionDefault
checksNoSubset of checks (default all).
domainYesDomains to audit (max 3).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, and openWorldHint, so the safety profile is covered. The description adds two genuinely useful facts beyond them: results come back as findings per check, and the call is capped at 3 domains. It stays silent on the higher-value behavioral questions for an audit tool — whether a failing sub-check aborts the whole call or degrades gracefully, how long an all-checks run takes, and whether results are cached between calls.

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 sentences, both earning their place: the first front-loads the verb and the full check inventory, the second carries the two behavioral facts (per-check findings, 3-domain cap). No filler, no restatement of the name or title.

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 and only two parameters, the description is close to sufficient: it names what each check covers and says results arrive as per-check findings. The remaining gap is the shape of a finding and what a partial or failed check looks like in the response, which an agent parsing results would want; that alone keeps it off a 5.

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 both parameters are documented in the schema, including the enum of check types and the default-all behavior, so the baseline is 3. The description's only parameter-adjacent sentence ("Up to 3 domains per call") restates the schema's maxItems:3 rather than adding meaning, and it never explains the tradeoff of selecting a check subset.

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?

"Audit a domain" gives a specific verb and resource, and the description enumerates the exact scope: DNS, SPF/DKIM/DMARC, TLS certificate, HTTP behavior, and robots.txt crawler rules. That enumeration also distinguishes it from the sibling check_domain_availability, which by name covers a different question (is it registered) rather than a configuration audit.

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 checks make it obvious you call this when you want a configuration audit, and "Up to 3 domains per call" sets a batching constraint. There is no explicit when-not guidance, no mention of the availability sibling as the alternative for registration questions, and no note on when to pass a subset of checks (e.g., a cheap TLS-only re-check).

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