Skip to main content
Glama

Reverse NS Lookup

ns_reverse
Read-onlyIdempotent

Reverse NS lookup: find domains hosted on a specific nameserver, filtered by TLD and keyword. Covers generic TLDs plus country-code TLDs; which country-code TLDs you can see depends on your plan, and asking for one outside it returns a message saying so. Give several nameservers to find domains that use all of them at once (intersection; available on higher plans).

Related: whois, dns.

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": {
      "ns": "<ns>"
    },
    "name": "ns_reverse"
  }
}

Input Schema

NameRequiredDescriptionDefault
nsYesTarget nameserver hostname (e.g., 'ns1.example.com'). Comma-separate up to 10 to match only domains that use all of them (intersection, unlike tld where commas mean any); multiple nameservers are available on higher plans.
tldNoFilter by TLD, matched as an exact suffix (e.g. 'com', 'de', or a second-level suffix such as 'co.uk'; 'uk' does not include 'co.uk')
pageNoPage number for pagination
sortNoSort order
keywordNoSubstring filter within domain names
max_lenNoMaximum domain name length (integer)
min_lenNoMinimum domain name length (integer)
no_hyphenNoExclude hyphens
no_numberNoExclude numbers
pure_alphaNoLetters only (strictest quality filter)
pure_digitNoNumbers only

Output Schema

NameRequiredDescriptionDefault
dataNo
pageNo
errorNo
totalNoNumber of results on this page
successNo
max_pageNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / tld / description
      Previous value: -"Filter by TLD (e.g., 'com')"New value: +"Filter by TLD, matched as an exact suffix (e.g. 'com', 'de', or a second-level suffix such as 'co.uk'; 'uk' does not include 'co.uk')"
  2. Changed1 schema field changed
    • removedOutput schema / required
      Removed value: -[
      -  "success"
      -]
  3. Changed1 schema field changed
    • changedInput schema / properties / ns / description
      Previous value: -"Target nameserver hostname (e.g., 'ns1.example.com')"New value: +"Target nameserver hostname (e.g., 'ns1.example.com'). Comma-separate up to 10 to match only domains that use all of them (intersection, unlike tld where commas mean any); multiple nameservers are available on higher plans."
  4. Added

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered; the description adds plan-gated ccTLD coverage and the fact that out-of-plan TLD requests return an explanatory message rather than silently failing. That is real behavioral context beyond the annotations, though rate limits and result-size/pagination behavior are not mentioned.

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?

Three compact sentences, front-loaded with the core operation, then filters, then plan caveats. The plan sentence is slightly wordy but carries non-obvious information, so little is wasted.

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 11 parameters, full schema coverage, an output schema, and rich annotations, the description covers the essentials an agent needs: scope, filtering, intersection semantics, and plan gating. Only pagination/result-size expectations and sibling routing are left implicit.

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 every parameter is already documented in the schema, including the intersection semantics of comma-separated nameservers. The description restates the intersection and TLD coverage at a high level but adds no syntax or format detail beyond the schema, so 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?

Opens with a specific verb+resource: 'Reverse NS lookup: find domains hosted on a specific nameserver,' then narrows scope with the TLD and keyword filters. An agent can distinguish this from whois/dns style lookups without opening the schema.

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

Usage Guidelines3/5

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

Explains the multi-nameserver intersection behavior and that higher plans are required, which shapes how to call it, but gives no explicit when-to-use/when-not guidance relative to siblings. The 'Related: whois, dns' line names alternatives without stating the condition that selects them.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.