Skip to main content
Glama

Lookproof DNS, mail and TLS security checks

Name server check

nameservers
Read-onlyIdempotent

Use when the user asks which name servers a domain uses, who hosts its DNS (from the NS names) or whether they are redundant. Returns the NS set with addresses (up to eight); flags a single server, unresolvable ones, one network and missing glue. Ex: 'Which name servers does example.com use?'. Free trial without an API key: a few calls a day.

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
domainYesA public domain name, e.g. example.com.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Annotations already cover safety (readOnly, idempotent, non-destructive, open-world), and the description adds genuinely new behavior: the result is capped at eight NS records with addresses, and specific anomalies are flagged (single server, unresolvable entries, one network, missing glue). It also discloses the access tier — a free trial without an API key limited to a few calls a day.

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?

Front-loaded with the trigger condition, then return behavior, then a concrete example, then the quota note — each sentence carries distinct information with no repetition of the title or name.

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?

There is no output schema, so the description must carry the return-value burden, and it does: record cap, address inclusion, and the specific anomaly flags. Combined with the quota/auth note, an agent has everything needed to select and call this correctly.

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?

Only one parameter exists and the schema fully documents it (maxLength 254, public domain, example.com). The description reinforces the intended input with the same worked example but adds no further constraint beyond the schema, which is the expected baseline here.

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 and resource — retrieve the name server (NS) set for a domain — plus what else it derives: DNS host from NS names and redundancy assessment. That scope distinguishes it from siblings like dns_lookup, mx, or dnssec without the agent opening any 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?

The opening clause enumerates concrete triggers: 'which name servers a domain uses', 'who hosts its DNS', 'whether they are redundant'. It gives no explicit when-not or named alternative (e.g. for arbitrary record types), so routing to a sibling remains partly inferential.

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.