Skip to main content
Glama

DomainKits

by io.github.ABTdomain

Newly Registered Domains Search

nrds
Read-onlyIdempotent

Search newly registered domains from the last 60 days by keyword, or browse a single TLD without a keyword. Filter by recency, registration term, length, character set, and sale status; returns the cross-TLD count for each name. New registrations are folded in continuously, typically 15 to 20 minutes after registration. Two coverage limits worth knowing: dates here are day-level, not clock times, and the 60-day history is gTLD-based, so country-code TLDs such as .ai and .io are present only for the last few days. When you need the exact registration time, the name split into words, or full country-code coverage, use nrds_live, which holds the last three days.

Related tools: nrds_live, whois, dns, ns_reverse, typosquat

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
tldNoFilter by TLD (e.g., 'com', 'ai', 'io')
pageNoPage number for pagination
sortNoSort order
typeNoCharacter set filter
lengthNoDomain name length filter
periodNoRegistration term length in years
excludeNoNegative keywords to exclude
keywordNoSearch term (min 2 chars). Substring matching applies at every length, including 2-character terms.
has_saleNoFilter to domains listed for sale
positionNoKeyword placement in domain name. Default is 'all' (substring match).
no_hyphenNoExclude hyphenated domains
no_numberNoExclude domains containing numbers
days_rangeNoRegistration recency
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. Matches the prefix_tld_count field in results. Domains first seen only hours ago (live rows) carry a count of 1.

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

TDQS

A4.7/5.0
Behavior5/5

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

Annotations already declare readOnly, idempotent, and non-destructive. The description adds valuable behavioral context beyond that: continuous ingestion with 15–20 minute delay, day-level date granularity, gTLD-based coverage with only partial ccTLD presence, and the note that live rows carry a count of 1. No contradiction with annotations.

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 dense but efficient. It front-loads the core purpose, then adds three chunks of high-value context (freshness, coverage limits, and sibling routing). No filler; every sentence earns its place. The structure guides the agent from 'what' to 'when' to 'alternatives'.

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 15 parameters, an output schema, and no required fields, the description covers the essential decision points: the two search modes, data freshness boundaries, coverage limitations, and the exact scenario where nrds_live should be used. It also mentions the returned cross-TLD count. An agent can correctly invoke this tool with the information provided.

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%, so the baseline is 3. The description does not elaborate on any specific parameter beyond listing filter categories ('recency, registration term, length, character set, and sale status') which the schema already documents. It adds no syntax or format details beyond what the schema provides.

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 opens with a clear, specific verb ('Search') and resource ('newly registered domains from the last 60 days'), then immediately distinguishes two modes (by keyword or by single TLD). It explicitly names the sibling alternative (nrds_live) and the conditions that select it, so an agent can differentiate without probing further.

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?

The description provides explicit routing: it names nrds_live as the alternative for exact registration time, word-split names, or full ccTLD coverage, and states that nrds itself is gTLD-based with day-level dates. This gives clear when-to-use and when-not-to-use guidance, exceeding the typical sibling differentiation.

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
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.

TDQS

A3.5/5.0
Disambiguation3/5

Many domain-search tools (active, aged, expired, deleted, market, nrds, nrds_live) have overlapping boundaries that depend on subtle lifecycle or listing distinctions, and pairs like bulk_tld/tld_check and nrds/nrds_live are easy to confuse. The detailed descriptions and related-tool hints help, but an agent still faces several nearly interchangeable choices.

Naming Consistency4/5

All tool names follow a consistent lowercase_snake_case convention, with no mixing of camelCase or inconsistent verb styles. However, the names use a noun/adjective pattern rather than a clear verb_noun action pattern, and acronyms like nrds, epp_status, and tld_rank make some names less predictable.

Tool Count2/5

32 tools is heavy for a domain toolkit, and several tools are close variants of the same search or check operation, such as active/aged/expired/deleted/market and nrds/nrds_live. The broad domain scope justifies some breadth, but the set would be much more focused with consolidation.

Completeness4/5

The toolset covers the core domain lifecycle well: availability, registration states, WHOIS, DNS, pricing, TLD statistics, safety, backlinks, typosquatting, and monitoring. The main gaps are that strategy can store data but has no retrieval or deletion action, and market pricing is limited to Sedo only.

Resources