Skip to main content
Glama

IP-DB IP Reputation

Domain WHOIS lookup

domain_whois
Read-onlyIdempotent

WHOIS/RDAP record of a domain from whois.ip-db.com: registrar, creation date (domain age), expiry date, status codes, nameservers, the hosting IPs with their ip-db.com reputation, subdomain count and a short security assessment (SPF, DMARC, TLS, transfer lock). Works for .com.tr and the other .tr domains.

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

Input Schema

NameRequiredDescriptionDefault
domainYesA registered domain name, e.g. example.com or ornek.com.tr

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?

Annotations already cover read-only, idempotent and open-world behavior, yet the description still adds real context: the upstream data source (whois.ip-db.com), the presence of enriched reputation data for hosting IPs, and a derived security assessment (SPF, DMARC, TLS, transfer lock). It does not disclose failure behavior (unregistered or unsupported domains) or latency, which keeps it below 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.

Conciseness5/5

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

Two sentences, front-loaded with what the tool is, followed by a compact field inventory and a scope note. The dense enumeration earns its space because no output schema exists to convey the returned fields.

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 single-argument read-only lookup with no output schema, the description supplies everything the agent needs: the resource, the data source, the returned fields including a security summary, and TLD coverage. Nothing essential is missing given the annotations carry the safety profile.

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?

With a single parameter at 100% schema coverage, the schema already defines the argument and gives examples. The description adds marginal value by clarifying TLD scope (.com.tr and other .tr domains), which extends the schema's example-only coverage but does not explain normalization rules for subdomains or URLs.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

"WHOIS/RDAP record of a domain" names a specific resource and retrieval verb, then enumerates the record contents (registrar, dates, status codes, nameservers, IPs, security assessment). It is unmistakable what the tool returns, though it never explicitly contrasts itself with the IP-oriented siblings check_ip/check_blacklists, leaving that distinction implicit in the resource type.

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 reader infers this is the tool for domain-level registration data, and the closing note that it "works for .com.tr and the other .tr domains" is a useful scope/coverage constraint. There is no explicit when-to-use versus check_ip or check_blacklists, and no stated preconditions such as needing a registered, not subdomain, name.

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