mcp-livedatapro

getDomainWhois

Real-time WHOIS and RDAP lookup for domain ownership, registrar, creation/expiry dates, and DNS nameservers. Use when inspecting an active or registered domain's WHOIS/RDAP ownership record, registrar, creation/expiration timestamps, and DNS nameservers. Do not use for discovering dropped/expired domains by keyword (use searchExpiredDomains) or IP geolocation (use getIpIntelligence). Queries authoritative registry RDAP servers in real time.

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

Input Schema

Name	Required	Description	Default
`domain`	Yes	Registered root domain name without protocol or path (e.g., openai.com, livedatapro.site).

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedOct 24, 2026
- addedInput schema / additionalProperties
```
Added value: +false
```
- addedInput schema / properties / domain / examples
```
Added value: +[
+  "openai.com"
+]
```
- addedInput schema / properties / domain / pattern
```
Added value: +"^[a-zA-Z0-9.-]+\\.[a-zA-Z]{2,}$"
```

Changed1 schema field changedOct 24, 2026

changedInput schema / properties / domain / description

Previous value: -"Domain name to query (e.g., openai.com, livedatapro.site)"New value: +"Registered root domain name without protocol or path (e.g., openai.com, livedatapro.site)."

First observedOct 21, 2026

TDQS

A4.1/5.0

Behavior3/5

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

With no annotations, the description carries the full burden. It does usefully disclose the data source and freshness ('queries authoritative registry RDAP servers in real time'), which tells the agent results are live rather than cached. But it says nothing about failure behavior for unregistered or privacy-redacted domains, rate limits, or whether the lookup is free or billed — meaningful gaps for a real-time network call.

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 the verb and resource, then usage rules, then exclusions — good ordering. It loses a point for mild redundancy: the field list (registrar, creation/expiry, nameservers) is stated in sentence one and restated in sentence two.

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?

No output schema exists, so the description usefully enumerates the returned fields, and the usage/exclusion guidance is complete. For a single-parameter read tool this is close to sufficient; only the not-found/redacted-domain behavior is unaddressed.

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 domain parameter already documents format, pattern, and an example, so the schema does the heavy lifting. The description reinforces the resource being looked up but adds no syntax or constraint detail beyond what the schema states; baseline 3 applies.

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 (lookup) and resource (WHOIS/RDAP record) plus the concrete fields returned (registrar, creation/expiry, nameservers). It explicitly distinguishes itself from searchExpiredDomains and getIpIntelligence, so an agent can pick it out of a 48-tool sibling list without opening a schema.

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 when-to-use clause (inspecting an active/registered domain's ownership record) and an explicit when-not with the named alternatives for both adjacent cases: keyword discovery of dropped domains and IP geolocation. Nothing 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.

All mcp-livedatapro tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?