Vee3

domains.lookup

Look up a domain and return normalized registration details.

Combines registry and registrar RDAP and WHOIS sources to return the most accurate normalized fields across TLDs: availability, domain status, created/updated/expiry dates, registrar data, contact records, and nameservers.

Use this when you need registrant-oriented summary data rather than raw WHOIS or RDAP payloads.

Cost = 5 tokens.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`domain`	Yes	Domain name to look up (for example example.com).

Output Schema

TableJSON Schema

Name	Required	Description
`tld`	No	Top-level domain suffix.
`dates`	No	Registration lifecycle dates.
`domain`	No	Looked-up domain name.
`source`	No	Primary data source used for the normalized response.
`status`	No	Normalized EPP status codes.
`keyword`	No	Second-level domain label without the TLD.
`contacts`	No	Registrant, admin, tech, and billing contact records.
`registrar`	No	Registrar summary data.
`nameservers`	No	Authoritative nameserver host names.
`availability`	No	Availability state (for example registered or available).

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

Changed4 schema fields changedJun 22, 2026

removedOutput schema / $defs / DomainsLookupResponseNameserversItem

Removed value: -{
-  "additionalProperties": true,
-  "properties": {
-    "nameserver": {
-      "anyOf": [
-        {
-          "type": "string"
-        },
-        {
-          "type": "null"
-        }
-      ],
-      "default": null,
-      "description": "Single nameserver host name.",
-      "title": "Nameserver"
-    }
-  },
-  "title": "DomainsLookupResponseNameserversItem",
-  "type": "object"
-}

removedOutput schema / $defs / DomainsLookupResponseStatusItem

Removed value: -{
-  "additionalProperties": true,
-  "properties": {
-    "status": {
-      "anyOf": [
-        {
-          "type": "string"
-        },
-        {
-          "type": "null"
-        }
-      ],
-      "default": null,
-      "description": "Single domain status value.",
-      "title": "Status"
-    }
-  },
-  "title": "DomainsLookupResponseStatusItem",
-  "type": "object"
-}

changedOutput schema / properties / nameservers / anyOf

Previous value: -[
-  {
-    "items": {
-      "$ref": "#/$defs/DomainsLookupResponseNameserversItem"
-    },
-    "type": "array"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "items": {
+      "type": "string"
+    },
+    "type": "array"
+  },
+  {
+    "type": "null"
+  }
+]

changedOutput schema / properties / status / anyOf

Previous value: -[
-  {
-    "items": {
-      "$ref": "#/$defs/DomainsLookupResponseStatusItem"
-    },
-    "type": "array"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "items": {
+      "type": "string"
+    },
+    "type": "array"
+  },
+  {
+    "type": "null"
+  }
+]

First observedJun 18, 2026

TDQS

A4.3/5.0

Behavior4/5

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

No annotations are provided, so the description must carry the burden. It explains that the tool combines registry and registrar RDAP/WHOIS sources and normalizes results, adding meaningful behavioral context beyond a simple lookup. It also notes the cost in tokens, which is helpful. However, it does not mention potential limitations like rate limits or TLD coverage.

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?

The description is four sentences, each earning its place: purpose, source/normalization details, usage guidance, and cost. It is front-loaded and concise without unnecessary fluff.

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?

Given the tool's low complexity (one parameter) and the existence of an output schema, the description is complete. It states what data is returned, how it is sourced, when to use it, and the token cost, providing sufficient context for an agent to select and invoke the tool.

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?

The schema already describes the single 'domain' parameter with an example, achieving 100% schema description coverage. The description does not add extra parameter-level details beyond the schema, so the baseline score of 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?

The description clearly states the tool looks up a domain and returns normalized registration details, listing specific fields (availability, status, dates, registrar, contacts, nameservers). It distinguishes itself from raw RDAP/WHOIS tools by emphasizing normalized, registrant-oriented summary data, which contrasts with sibling tools like domains.rdap and domains.whois.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description explicitly says to use this when registrant-oriented summary data is needed rather than raw WHOIS or RDAP payloads. It gives clear context for when this tool is appropriate, though it does not explicitly name the sibling tools as alternatives.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Vee3 tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.