Skip to main content
Glama
Sign In

IntoDNS.ai DNS & Email Security Scanner

by ai.intodns
OverviewDiscussionsAdmin

DNS record lookup

lookup_dns
Read-onlyIdempotent

Read-only DNS record lookup via DNS-over-HTTPS. Pass type for a single record type or types for an array; if both omitted, returns A records. Returns parsed answers with TTL, raw rdata, and DNSSEC AD bit. Use for arbitrary record queries; use validate_dnssec for full DNSSEC chain validation, or check_dns_propagation for multi-resolver consensus. No auth, no rate limits beyond upstream resolver.

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

Input Schema

NameRequiredDescriptionDefault
typeNoSingle DNS record type
typesNoMultiple DNS record types
domainYesDNS name, e.g. example.com, _spf.google.com or _dmarc.example.com (no URL, path, or port)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / domain / description
      Previous value: -"Domain name only, e.g. example.com (no URL, path, or port)"New value: +"DNS name, e.g. example.com, _spf.google.com or _dmarc.example.com (no URL, path, or port)"
  2. First observed

TDQS

A4.9/5.0
Behavior5/5

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

Beyond the readOnly/idempotent/openWorld annotations, it discloses the DoH transport, the default-to-A behavior when type and types are both omitted, the exact return shape (parsed answers with TTL, raw rdata, DNSSEC AD bit), and the absence of auth and rate limits except upstream resolver limits. That is meaningful operational context an agent can't get from the annotations.

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?

Three dense sentences, front-loaded with what the tool is, then parameter behavior, then return contract, then sibling routing. Every clause carries information; no filler.

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 present, the description compensates by naming the returned fields (TTL, raw rdata, AD bit). Combined with the defaulting rule, auth/rate-limit statement, and sibling alternatives, an agent has everything needed to call it correctly.

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 description coverage is 100%, so the baseline is 3, but the description adds real semantics the schema lacks: the mutual-exclusivity framing of type vs types and the default of A records when both are omitted. The 'no URL, path, or port' hint for domain is also enforced in the schema, so only the defaulting rule is genuinely new.

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 record lookup') plus the transport ('via DNS-over-HTTPS'), which immediately separates it from siblings like validate_dnssec and check_dns_propagation. An agent knows exactly what the tool does 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 Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly routes to alternatives with conditions: 'use validate_dnssec for full DNSSEC chain validation, or check_dns_propagation for multi-resolver consensus', and declares the generic case ('Use for arbitrary record queries'). Nothing is left to inference about when this is the right pick.

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

All IntoDNS.ai DNS & Email Security Scanner 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