dns_lookup
Full DNS record dump (A/AAAA/MX/NS/TXT/SOA/CAA/CNAME) for a host. (domain-dns; $0.003/call in USDC via x402, 50 free/day).
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| host | Yes | Target URL or hostname. |
fetcher
TDQS
A3.7/5.0
Behavior4/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations provided, so the description carries full burden. It discloses cost and free tier, and implies read-only behavior. However, it does not mention error handling, output format, or rate limits beyond the free tier.
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?
The description is a single, front-loaded sentence that conveys the core functionality and pricing. Every phrase serves a purpose with no repetition.
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?
For a simple lookup tool, the description is adequate but lacks guidance on when to choose it over siblings (e.g., check_domain for availability, whois_lookup for registration info). No output schema or annotations, so some behavioral details are missing.
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?
The single parameter 'host' is fully described in the schema as 'Target URL or hostname.' The description adds no additional semantic value, and schema coverage is 100%, giving a baseline of 3.
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?
The description clearly states the tool returns a 'Full DNS record dump' for a host, listing all record types (A/AAAA/MX/NS/TXT/SOA/CAA/CNAME). This distinguishes it from siblings like whois_lookup or check_domain.
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 explicit guidance on when to use this tool versus alternatives. The description does not mention when not to use it or refer to other tools (e.g., check_domain, whois_lookup) for related tasks.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Try in Browser
Glama MCP Gateway
Add one secure layer between your agents and this server.
TDQS
B3.4/5.0
Disambiguation4/5
Most tools have clearly distinct purposes, but there are overlapping pairs: unfurl_url/get_oembed/find_favicon all provide URL metadata, and render_page/screenshot_page both render a page (render_page can also screenshot). Descriptions help disambiguate, so only minor confusion is likely.
Naming Consistency3/5
Tool names mix verb_noun patterns (check_domain, extract_content) with noun_verb patterns (dns_lookup, ssl_lookup, whois_lookup). Additionally, guard_inspect and guard_tx deviate from the typical verb-first style. The naming is readable but not consistent.
Tool Count3/5
With 19 tools, the server is at the heavier end of the scale. While it covers a broad web-intel toolkit, several tools feel out of place for a 'fetcher' (e.g., generate_qr, guard_tx, guard_inspect), making the set feel bloated and unfocused.
Completeness4/5
The core web-fetching and analysis surface is well covered: DNS, WHOIS, SSL, headers, content extraction, rendering, screenshots, feeds, embeds, redirects, and robots. Missing is a simple raw HTML fetcher, but extract_content and render_page likely cover most needs. The addition of security and utility tools doesn't fill obvious gaps.