Crawlora MCP

domain_dns_resolve

Read-only

Resolve one Google Public DNS query for a name and record type. The response includes the resolver code, DNSSEC authenticated-data flag, and typed answers with TTLs. Use domain_dns_record_types to discover supported types.

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>",
      "type": "<type>"
    },
    "name": "domain_dns_resolve"
  }
}

Input Schema

Name	Required	Description	Default
`name`	Yes	Bare public DNS name, including service labels such as _dmarc; required.
`type`	Yes	One DNS record type. Use domain_dns_record_types to discover the complete supported set.

Output Schema

Name	Required	Description	Default
`data`	Yes	The tool result payload (shape varies per tool; see each tool's docs resource).

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 7, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, so the safety profile is covered. The description still adds value by pinning the call to exactly one query for one record type, so an agent knows it must call repeatedly for multi-type lookups, and by naming the DNSSEC authenticated-data flag as part of the result.

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 short sentences, the operation front-loaded, the scope constraint second, the sibling redirect last. Nothing is padded and every clause carries information.

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?

For a two-parameter read tool with an output schema, the definition covers what the call does and what the result contains. Failure modes such as NXDOMAIN or SERVFAIL are not mentioned, but the resolver-code field in the described response hints at them.

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 coverage is 100% and both parameter descriptions already cover the bare-name rule, the _dmarc service-label case, and the record-type discovery pointer. The description restates 'name and record type' and adds no format or example detail beyond the schema, so baseline 3 applies.

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 ('Resolve one Google Public DNS query') plus the exact scope (a single name and record type). It also names the sibling tool that supplies the type vocabulary, so an agent can place it precisely among the domain_* tools.

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?

Explicitly routes the agent to domain_dns_record_types when the record type is unknown, which is the main pre-call ambiguity. It does not contrast itself against the other domain siblings (rdap, subdomains, wayback), but the single-lookup scope makes the boundary obvious enough.

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

All Crawlora MCP 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?