Skip to main content
Glama

Managed Nerds

check_domain

Read-onlyIdempotent

Free domain health check (also accepts an email or website address): when the domain expires and who it's registered with, whether it's locked against transfer, its name servers, whether the website loads over https and redirects http, www vs the bare domain, CAA, and DNSSEC as a note. Grades it (good, needs work, at risk) with exactly what to fix. Public data only (registration data, DNS, one request to the home page); auto-renew and certificate expiry can't be seen from outside. No contact details; the domain and result are kept 90 days, nothing about who asked. 10 checks an hour per address.

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

Input Schema

NameRequiredDescriptionDefault
domainYesexample.com, you@example.com or https://example.com

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior5/5

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

Goes well beyond the annotations: discloses the data-access footprint (public registration data, DNS, one request to the home page), explicit blind spots (auto-renew and certificate expiry can't be seen from outside), privacy handling (no contact details, 90-day retention, nothing about who asked), and a rate limit of 10 checks/hour per address. These are exactly the operational facts an agent needs before invoking a networked check.

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?

Purpose and input flexibility are front-loaded, and every later clause carries real information (checks, limitations, privacy, rate limit). It is a single dense run-on sentence chain rather than clearly separated lines, which slightly hurts scanability but not content efficiency.

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?

For a one-parameter, no-output-schema tool, this covers what is checked, what the result looks like (a good/needs-work/at-risk grade plus exactly what to fix), what cannot be determined, and the privacy/rate constraints. Nothing an agent needs to call it correctly or set expectations 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 parameter's schema description already gives the accepted formats ('example.com, you@example.com or https://example.com'). The description's acceptance note largely restates that, adding only the framing that email and web addresses are normalized to a domain; baseline 3 is 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?

States a specific verb and resource ('Free domain health check') and then enumerates the actual checks performed: expiry, registrar, transfer lock, name servers, HTTPS/redirect behavior, www vs bare domain, CAA, DNSSEC. The enumerated scope makes it clearly distinct from siblings like check_email_security or check_ai_readiness 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?

The parenthetical 'also accepts an email or website address' implies when the tool applies (you have a domain, email address, or URL), but there is no explicit when-to-use/when-not guidance and no routing to alternatives. Usage is inferable rather than stated.

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