x402-dns-all
DNS All: Full DNS lookup — all record types.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| domain | No | Domain to process |
minia2a-mcp
by uk.minia2a
TDQS
A3.8/5.0
Behavior3/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the burden. It conveys the core read-only lookup behavior, but does not disclose output format, error behavior, network dependency, or rate-limit considerations.
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?
One tightly worded sentence that front-loads the purpose and scope with zero filler.
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 single-parameter, simple lookup tool, the description plus schema are mostly sufficient. A brief note about the return structure or whether all records are grouped by type would make it fully complete.
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%, and the domain parameter already has 'Domain to process'. The tool description adds no further meaning about parameter format, validation, or requiredness beyond the schema.
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?
Description states a specific operation ('Full DNS lookup') and explicit scope ('all record types'). This clearly distinguishes it from narrower sibling tools like cname-lookup, mx-lookup, and dns-lookup.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines3/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
The 'all record types' phrasing weakly implies use when comprehensive DNS coverage is needed, but there is no explicit guidance about when to choose this tool over siblings or when a narrower lookup would suffice.
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
D1.6/5.0
Disambiguation1/5
The tool set is saturated with near-duplicates and synonyms: character-count vs char-count, clamp vs clamp-value, is-abundant vs is-abundant-num vs is-abundant-number, and fetch vs browser-scrape vs web-scrape vs text-scrape. Generic names like 'difference', 'normalize', 'range', and 'partition' make the boundaries even harder for an agent to determine.
Naming Consistency2/5
Most tools share a x402- kebab-case prefix, but the set mixes noun-only names (math, hash, prime, time), verb-first names (get_stats, find, validate), auto-generated names (x402-publish-1787853294312-base-account), and inconsistent variants like temp vs temperature vs temperature-convert. This is not a coherent verb_noun convention despite the common prefix.
Tool Count1/5
1677 tools is an extreme count that creates selection paralysis and makes coherent agent use impractical. A utility or marketplace server at this scale needs sub-services or namespacing rather than a flat tool list.
Completeness2/5
The surface has broad token coverage across many utility categories, but the marketplace aspect is incomplete: service_discovery and get_stats exist, yet there are no generic publish, update, delete, or account-management operations. Utility families also contain redundant variants without clear completion or lifecycle structure.