Retrieve all DNS resource records for a domain zone to inspect or audit current DNS configuration. Use it to verify A, MX, TXT, and other records before making changes.
Get all DNS resource records for a domain zone.
| Name | Required | Description | Default |
|---|---|---|---|
| domain_name | Yes | Domain name |
Changes observed during successful MCP inspections.
v1.0.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full behavioral burden. While 'Get' implies a read-only operation, the description does not disclose return format, pagination behavior, zone scoping semantics, or any permission requirements.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
A single, efficiently front-loaded sentence with no wasted words. It states the action and scope immediately.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a simple one-parameter read tool the description is roughly adequate, but with no output schema and no annotations it does not explain the return shape, and it omits the sibling differentiation needed to choose between the several DNS-reading tools.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100% for the single domain_name parameter, so the baseline is 3. The phrase 'for a domain zone' slightly clarifies that domain_name identifies the zone, but adds little beyond the schema.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description states a specific verb ('Get') and resource ('all DNS resource records for a domain zone'), making the operation clear on its own. However, it fails to distinguish itself from the very similar sibling regru_get_domain_dns, leaving the agent unable to tell them apart without consulting schemas.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
There is no indication of when to use this tool versus alternatives like regru_get_domain_dns or regru_get_domain_dns, and no prerequisites or exclusions are stated. The agent must infer usage entirely from the name.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.