Skip to main content
Glama

DomainKits

by io.github.ABTdomain
OverviewDiscussionsAdmin

Active Domain Search

active
Read-onlyIdempotent

Search active gTLD domains from a database of ~240 million registered domains, filtered by keyword, TLD, length, and character set. A market-analysis instrument for keyword distribution and saturation; results are registered domains, not available for registration.

Related: expired, whois, dns.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
tldNoFilter by TLD (e.g., 'com', 'net', 'org'); when keyword is omitted, this is the browse target (TLD browse mode requires a registered account)
pageNoPage number for pagination
sortNoSort order
typeNoCharacter set filter
lengthNoDomain name length filter
statusNoFilter by status: 'forsale' for domains listed for sale
keywordNoBrand or industry term (min 2 chars). Omit to use TLD browse mode, which requires a registered account.
positionNoKeyword placement in domain name. Default is 'all' (substring match). Unlike the other search tools, this one has no minimum-length restriction on substring matching.
no_hyphenNoExclude hyphenated domains (true/false)
no_numberNoExclude domains containing numbers (true/false)
tld_count_maxNoMaximum cross-TLD registration count for the name. Integer 0-10000. See tld_count_min.
tld_count_minNoMinimum cross-TLD registration count for the name. Integer 0-10000. Combine with tld_count_max for a range; set both equal for an exact count.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
dataNo
pageNo
errorNoError message when success is false
totalNoNumber of results on this page
successYes
max_pageNo
total_foundNoTotal matching results across all pages; the primary metric for comparative analysis

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / properties / data / items / properties / marketplace / description
      Previous value: -"Sale platform code where the domain is listed: se=Sedo, go=GoDaddy, at=Atom, vn=Venture, pd=PerfectDomain, gn=Gname. Present only when the domain is listed for sale."New value: +"Sale platform code where the domain is listed: se=Sedo, go=GoDaddy, at=Atom, vn=Venture, pd=PerfectDomain, gn=Gname, hu=HugeDomains. Present only when the domain is listed for sale."
  2. Changed1 schema field changed
    • changedOutput schema / properties / total_found / description
      Previous value: -"Total matching results across all pages — primary metric for comparative analysis"New value: +"Total matching results across all pages; the primary metric for comparative analysis"
  3. Changed2 schema fields changed
    • changedInput schema / properties / keyword / description
      Previous value: -"Brand or industry term (min 2 chars). Omit to use TLD browse mode."New value: +"Brand or industry term (min 2 chars). Omit to use TLD browse mode, which requires a registered account."
    • changedInput schema / properties / tld / description
      Previous value: -"Filter by TLD (e.g., 'com', 'net', 'org'); when keyword is omitted, this is the browse target"New value: +"Filter by TLD (e.g., 'com', 'net', 'org'); when keyword is omitted, this is the browse target (TLD browse mode requires a registered account)"
  4. Changed2 schema fields changed
    • addedInput schema / properties / tld_count_max
      Added value: +{
+  "description": "Maximum cross-TLD registration count for the name. Integer 0-10000. See tld_count_min.",
+  "type": "string"
+}
    • addedInput schema / properties / tld_count_min
      Added value: +{
+  "description": "Minimum cross-TLD registration count for the name. Integer 0-10000. Combine with tld_count_max for a range; set both equal for an exact count.",
+  "type": "string"
+}
  5. Changed5 schema fields changed
    • changedInput schema / properties / length / enum
      Previous value: -[
-  "<5",
-  "5-10",
-  "11-15",
-  ">15"
-]New value: +[
+  "<5",
+  "5-10",
+  "11-15",
+  "15+"
+]
    • changedInput schema / properties / position / description
      Previous value: -"Keyword placement in domain name. Default is 'start' (prefix match) — pass position=contain explicitly for substring matching. Unlike the other search tools, this one has no minimum-length restriction on substring matching."New value: +"Keyword placement in domain name. Default is 'all' (substring match). Unlike the other search tools, this one has no minimum-length restriction on substring matching."
    • changedInput schema / properties / position / enum
      Previous value: -[
-  "start",
-  "end",
-  "middle",
-  "contain"
-]New value: +[
+  "start",
+  "end",
+  "middle",
+  "all"
+]
    • changedInput schema / properties / status / description
      Previous value: -"Filter by status — 'forsale' for domains listed for sale"New value: +"Filter by status: 'forsale' for domains listed for sale"
    • addedInput schema / properties / status / enum
      Added value: +[
+  "forsale"
+]
  6. Changed1 schema field changed
    • changedInput schema / properties / position / description
      Previous value: -"Keyword placement in domain name. Default is 'contain' (substring match)."New value: +"Keyword placement in domain name. Default is 'start' (prefix match) — pass position=contain explicitly for substring matching. Unlike the other search tools, this one has no minimum-length restriction on substring matching."
  7. Added

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is covered. The description adds genuine context beyond that: the ~240M domain corpus size, the market-analysis framing, and the crucial caveat that returned domains are registered (not acquirable). It omits auth/account requirements and pagination behavior.

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?

Two tight sentences front-load what the tool is and its most important caveat, followed by a compact 'Related:' routing line. No filler, though the Related line is slightly thin compared to a full alternatives statement.

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 an output schema present, return values need no explanation, and all 12 parameters are covered by the schema and annotations. The description supplies the essential framing (market analysis, registered-not-available) an agent needs to select it correctly; only explicit alternative-routing guidance 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 description coverage is 100%, so all 12 parameters are documented in the schema itself. The description only restates the filter categories (keyword, TLD, length, character set) without adding syntax or defaults, so the baseline of 3 applies when structured data does the heavy lifting.

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+resource ('Search active gTLD domains') with concrete scope ('~240 million registered domains') and enumerates the filter dimensions. It explicitly distinguishes itself from the sibling 'available' tool by clarifying results are 'registered domains, not available for registration', so an agent can tell it apart 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 Guidelines4/5

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

Frames the use case as 'a market-analysis instrument for keyword distribution and saturation' and clarifies the registered-vs-available distinction, which implicitly routes registration checks to 'available'. It names related tools (expired, whois, dns) but stops short of explicit when-to-use/when-not phrasing for each alternative.

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

All DomainKits toolsInspect
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