Skip to main content
Glama
offsec-mcp

offsec-mcp

by nadirzhon

Dns Lookup

dns_lookup

Resolve A, AAAA, MX, NS, TXT, and CNAME records for a domain via DNS-over-HTTPS to support reconnaissance and record analysis.

Instructions

Resolve A/AAAA/MX/NS/TXT/CNAME records for a domain (via DNS-over-HTTPS).

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_lookup"
  }
}

Input Schema

NameRequiredDescriptionDefault
domainYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior3/5

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

With no annotations, the description carries the disclosure burden; it does state the transport (DNS-over-HTTPS), which is genuinely useful context. However, it never states that the operation is read-only, whether lookups are rate-limited or logged, or how NXDOMAIN/timeouts are surfaced.

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?

One sentence, front-loaded with the verb and fully informative about record coverage and transport. No waste, though the parenthetical transport note is the only secondary detail.

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

Completeness3/5

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

An output schema exists, so return values need not be explained. Missing is what an agent needs to call correctly: whether all listed record types are always fetched or a subset returned, and how failures are reported for a low-complexity but network-dependent lookup.

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?

Only one parameter (domain) with 0% schema description coverage, so the description should clarify accepted format (bare domain vs FQDN, trailing dot, IDN/punycode) but does not. The enumerated record types at least suggest no type selector is needed, but the parameter itself remains undescribed.

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?

Names a specific verb (Resolve) and resource (DNS records for a domain) and enumerates the supported record types, which is enough for an agent to know exactly what it does. It does not differentiate itself from siblings like whois or recon_subdomains, but the operation is distinct enough by name.

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?

No guidance on when to use this versus whois, recon_subdomains, or http_probe, and no exclusions or prerequisites. The agent must infer that this is the tool for raw DNS record resolution from the name alone.

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