Skip to main content
Glama
Sign In

APIVerve

by com.apiverve
OverviewDiscussionsAdmin

Nameservers

Nameservers
Read-only

Nameservers: Nameservers queries authoritative DNS records for any domain to list its nameservers, IP addresses, and reverse DNS records. It detects multiple DNS providers, counts total nameservers, and identifies who runs each server. (Cost: 10 credits)

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": {
      "domain": "<domain>"
    },
    "name": "Nameservers"
  }
}

Input Schema

NameRequiredDescriptionDefault
domainYesThe domain name to lookup nameservers for

Output Schema

NameRequiredDescriptionDefault
dataNo
errorNoError message, null on success
statusNo"ok" on success

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, openWorldHint=true, and destructiveHint=false, so safety is covered; the description adds genuinely new behavioral context by disclosing a cost of 10 credits and characterizing what the query surfaces (authoritative records, multiple providers detected). It does not mention rate limits or failure behavior for non-existent or unregistered domains.

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 sentences of roughly equal weight, front-loaded with the core action; every clause carries information. Minor waste from restating the tool name twice at the start and a parenthetical cost note rather than integrating price into the flow.

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 one-parameter, read-only lookup with an output schema, annotations, and a stated credit cost, the description covers action, output shape, and price. Nothing essential to calling it correctly is missing given the structured fields that accompany it.

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?

There is a single parameter with 100% schema description coverage, so the schema already carries the semantics. The description adds only the mild clarification "for any domain," which hints that bare domains (not URLs) are expected but does not spell out subdomain or IDN handling. Baseline 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description uses a specific verb and resource ("queries authoritative DNS records ... to list its nameservers, IP addresses, and reverse DNS records") and enumerates the derived outputs (provider detection, count, operator). It is clear what the tool does without opening the schema, though it never distinguishes itself by name from DNS-adjacent siblings like DNSLookup, MXLookup, or ReverseDNSLookup.

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

Usage Guidelines2/5

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

Usage is only implied by the scope phrase "for any domain" — there is no statement of when to prefer this over DNSLookup, MXLookup, NSLookup-style siblings, or ReverseDNSLookup, even though this catalog contains many. No prerequisites, exclusions, or alternative routing are given.

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

All APIVerve 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