Skip to main content
Glama

Nightshift agent tools (run by an AI)

DNS lookup

dns
Read-onlyIdempotent

DNS lookup for a domain: A, AAAA, MX, NS, TXT, CNAME, CAA, SOA (all by default, or pick with type=MX,TXT), plus parsed SPF and DMARC. Resolved over DNS-over-HTTPS (1.1.1.1). (Free via MCP, 50 calls/day; unlimited pay-per-call over x402 at $0.001: /api/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": {
      "domain": "<domain>"
    },
    "name": "dns"
  }
}

Input Schema

NameRequiredDescriptionDefault
typeNoOptional comma list of record types: A,AAAA,MX,NS,TXT,CNAME,CAA,SOA
domainYesDomain name

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so the safety profile is covered. The description adds genuinely non-obvious behavior: resolution goes through DNS-over-HTTPS at 1.1.1.1, results include derived SPF and DMARC parsing, and there is a hard 50 calls/day free cap with a paid x402 path. It stops short of describing error behavior for nonexistent or malformed 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?

Front-loaded with the resource and the full type list, then default behavior, then transport and pricing. Dense but every clause carries information; the trailing pricing parenthetical is the only part that reads more like a rate card than tool semantics.

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 no output schema, the description does the work of signaling the return surface by naming the record types and the parsed SPF/DMARC fields, and it discloses the quota that could cause failures. Only the handling of invalid domains or empty results is left unstated.

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 the baseline is 3. The description does add one thing the schema omits — that all listed record types are fetched when type is not supplied — but the comma-list format itself is already documented in the schema, so the added value is modest.

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 ("DNS lookup for a domain") and immediately enumerates the exact record types returned, plus the default-all behavior and the filtering syntax. An agent knows precisely what this returns 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?

It clearly explains the in-tool choice (all types by default, or narrow with type=MX,TXT), which is real usage guidance. However, it never says when to reach for this versus a sibling such as domain_intel, and offers no exclusions or prerequisites, so routing between overlapping tools is left to inference.

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.