Skip to main content
Glama

DomainKits

by io.github.ABTdomain
OverviewDiscussionsAdmin

Live Newly Registered Domains

nrds_live
Read-only

Search newly registered domains from a live feed with exact registration and expiry timestamps; names usually appear within minutes of registration. Covers generic TLDs plus these country-code TLDs: .ai, .io, .co, .si, .sh, .so, .cc, and .br, .mx, .cl, .gg, .id, .my including their second-level registrations such as .com.br and .co.id (tld 'br' returns the whole .br family; combine it with a keyword); government, military, education and non-profit categories are not included. Which country-code TLDs you can see depends on your plan; asking for one outside it returns a message saying so. The listed country-code TLDs reach back 60 days, while generic TLDs cover only the last few days, so this tool works best for the most recent three days. Use nrds instead for older generic-TLD history, for filtering by a second-level suffix such as com.br, for registration-term or for-sale filters, for the cross-TLD count, or for deeper paging.

Related tools: nrds, whois, dns, typosquat

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
tldNoFilter by a single TLD without dots (e.g., 'com', 'ai', 'io'). 'br', 'mx', 'cl', 'gg', 'id' or 'my' covers that country's whole family; combine it with a keyword. One TLD per call; omit to cover all TLDs.
pageNoPage number for pagination. The live feed pages through the first 10000 matches; narrow the filters to reach beyond that.
sortNoSort order. Default is reg_date_desc (most recent first).
typeNoCharacter set filter
lengthNoDomain name length filter
excludeNoNegative keywords to exclude, comma-separated
keywordNoSearch term, 2-64 characters, letters/digits/hyphens only. Matches anywhere in the name unless position is set.
positionNoKeyword placement in domain name. Default is 'all' (substring match). Requires keyword.
no_hyphenNoExclude hyphenated domains
no_numberNoExclude domains containing numbers

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / tld / description
      Previous value: -"Filter by a single TLD without dots (e.g., 'com', 'ai', 'io'). One TLD per call; omit to cover all TLDs."New value: +"Filter by a single TLD without dots (e.g., 'com', 'ai', 'io'). 'br', 'mx', 'cl', 'gg', 'id' or 'my' covers that country's whole family; combine it with a keyword. One TLD per call; omit to cover all TLDs."
  2. Changed1 schema field changed
    • changedInput schema / properties / tld / description
      Previous value: -"Filter by a single TLD (e.g., 'com', 'ai', 'io'). One TLD per call; omit to cover all TLDs."New value: +"Filter by a single TLD without dots (e.g., 'com', 'ai', 'io'). One TLD per call; omit to cover all TLDs."
  3. Changed1 schema field changed
    • removedOutput schema / properties / data / items / properties / components
      Removed value: -{
-  "description": "Word segmentation of the name, space-separated. Absent when the feed supplies none.",
-  "type": "string"
-}
  4. Added

TDQS

A4.8/5.0
Behavior5/5

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

Annotations only declare readOnly/openWorld/idempotent/destructive hints; the description adds real behavioral context beyond them: plan-gated TLD visibility with an explicit error-message behavior, a 60-day vs few-day coverage asymmetry between ccTLD and generic TLDs, and category exclusions (government, military, education, non-profit). This is unusually rich disclosure for a read-only tool.

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 purpose and scope before the alternative-tool routing, and every sentence carries information. It is dense and long for an MCP description, with the TLD coverage enumeration consuming considerable space, but nothing is pure padding.

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 10-parameter zero-required open-world search with an output schema present, the description covers everything the agent needs: coverage windows, plan limits, family-TLD behavior, category exclusions, and alternate-tool routing. Return-value explanation is correctly omitted since an output schema exists.

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?

Schema coverage is 100%, so the baseline is 3, and the description does contribute cross-parameter semantics: the 'br'-style family behavior when combined with a keyword, and the practical paging limit ('narrow the filters to reach beyond' 10000 matches). However, most filter semantics (sort, length, type, position, exclude) are left entirely to the schema, so it earns only a modest lift over baseline.

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?

Opens with a specific verb+resource ('Search newly registered domains from a live feed') and immediately narrows scope with timestamps and freshness ('names usually appear within minutes of registration'). It also explicitly distinguishes itself from the sibling nrds, so an agent can route correctly 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 explicit when-to-use conditions (best for the most recent three days; ccTLDs reach back 60 days) and a detailed when-not-to-use list routing to nrds for older generic-TLD history, second-level suffixes, registration-term/for-sale filters, cross-TLD counts, and deeper paging. It also warns that which ccTLDs are visible depends on the plan and what happens when one is out of plan.

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