TPC Hosting Free Tools

Dig (DNS query)

dig

Read-onlyIdempotent

Sends a DNS query like the dig command, to Cloudflare, Google, Quad9 or a nameserver you name, and returns the full answer with flags and sections. Supports many record types, DNSSEC data and TCP.

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

Input Schema

Name	Required	Description
`ns`	No	Nameserver name or IP, only with server=custom.
`tcp`	No	Use TCP instead of UDP.
`name`	Yes	The name to look up, such as example.com, or an IP address for a PTR lookup.
`type`	No	Record type. Defaults to A.
`norec`	No	Turn recursion off (the +norec option), to ask an authoritative nameserver directly.
`dnssec`	No	Ask for DNSSEC records (the DO flag).
`family`	No	IP family to use. Defaults to auto.
`server`	No	Resolver to ask. Defaults to cloudflare. Use custom with ns for a specific nameserver.

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 11, 2026

TDQS

A3.6/5.0

Behavior4/5

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

Annotations already cover safety and idempotency. The description adds useful behavioral detail: it returns the full answer with flags and sections and supports DNSSEC, TCP, and multiple 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.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two tight sentences with the core purpose front-loaded and no filler. Supported features are summarized efficiently.

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?

Given rich schema coverage and annotations, the description is largely complete: it explains the query behavior, resolver options, and return shape. The main gap is lack of routing guidance against similar DNS tools, which keeps it from a 5.

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 schema already documents all parameters. The description only lightly restates resolver choices, record types, DNSSEC, and TCP without adding meaningful semantics beyond the schema.

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?

States a specific verb and resource ('Sends a DNS query') and identifies the dig-like behavior and resolver options. It does not explicitly distinguish itself from similar siblings such as dns_lookup or dns_trace, so it falls short of a 5.

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?

Provides no explicit when-to-use or when-not-to-use guidance. It mentions resolvers and features, but does not tell an agent how to choose this tool over sibling DNS tools.

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

All TPC Hosting Free Tools tools Inspect

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

Need Help?