Skip to main content
Glama
kali-mcp-server

kali-mcp-server

by rangta10

dig_dns

Perform DNS lookups for a domain using the dig command to retrieve A, AAAA, MX, NS, TXT, CNAME, or SOA records.

Instructions

Perform DNS lookup using dig command

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": "dig_dns"
  }
}

Input Schema

NameRequiredDescriptionDefault
domainYesDomain name to query
record_typeNoDNS record type (A, AAAA, MX, NS, TXT, CNAME, SOA)A

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.8/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full disclosure burden, and it discloses very little. Mentioning 'dig command' hints that a shell utility is executed and raw text output is returned, but nothing is said about timeout behavior, resolver used, error/failure output, or whether results are truncated.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

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

A single front-loaded sentence with no wasted words, which is good, but its brevity comes from omission rather than discipline. It is under-specified for a tool with no annotations and no output schema.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no annotations and no output schema, the description is the only place an agent could learn what comes back and how failures appear, and it says nothing about either. For such a simple two-parameter tool the gap is small but real.

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%, with both 'domain' and 'record_type' documented in the schema including the allowed record types and the default of 'A'. The description adds nothing beyond that, so the baseline of 3 applies rather than a lower score.

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 ('Perform DNS lookup') and names the underlying mechanism ('dig command'), so the agent knows exactly what operation runs. It does not, however, distinguish itself from siblings such as dns_enum or whois_lookup, so the agent gets no help on when this is the right lookup tool rather than another.

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?

There is no when-to-use or when-not-to-use guidance and no named alternative. The agent must infer on its own whether a single-record dig lookup is preferable to dns_enum for enumeration or whois_lookup for registration data.

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