Skip to main content
Glama
Sign In

Nightshift Labs: link, token & signature pre-checks

by dev.workers.nightshift-labs.nightshift-x402
OverviewDiscussionsAdmin

domain_dns_batch

Read-only

DNS lookup for up to 12 domains in ONE paid call: A, AAAA, MX and NS by default (or the types you ask for), NXDOMAIN status, DNSSEC validation and SPF/verification hints per name, plus a summary of which names resolve, which are NXDOMAIN and which have MX. Resolved via DNS-over-HTTPS. names x types must be <= 48. Price: $0.003 USDC on Base per call (x402).

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": {
      "names": "<names>"
    },
    "name": "domain_dns_batch"
  }
}

Input Schema

NameRequiredDescriptionDefault
namesYescomma list of 1-12 domain/host names
typesNooptional comma list of A,AAAA,CNAME,MX,TXT,NS,CAA,SOA (default A,AAAA,MX,NS)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.6/5.0
Behavior5/5

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

Annotations only say readOnly and openWorld; the description adds the material facts an agent needs: paid call at $0.003 USDC on Base per call via x402, DNS-over-HTTPS resolution, the names x types <= 48 ceiling, and default record types.

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 batch-and-cost hook and packed into essentially one dense sentence with no filler; slightly overstuffed with output detail, but every clause carries information.

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?

With no output schema, the description correctly summarizes what comes back (per-name records, NXDOMAIN status, DNSSEC, SPF hints, resolution summary) and covers cost, limits and transport, leaving no gap an agent would trip on.

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?

Schema coverage is 100% so both params are documented, but the description still adds the cross-product constraint (names x types <= 48) and restates the default type set, which is real meaning beyond the per-parameter text.

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 specific verb and resource ("DNS lookup") plus a hard scope differentiator ("up to 12 domains in ONE paid call"), which separates it from the single-name sibling domain_dns without the agent needing to open either 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?

It makes batch usage clear via the 12-name cap and the cost framing, implying single lookups belong elsewhere, but it never explicitly names domain_dns as the alternative for one-name queries or states a when-not-to-use condition.

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

All Nightshift Labs: link, token & signature pre-checks 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