Skip to main content
Glama

whm_dns_zone_records

Get all DNS records for a domain from a WHM server. Provide the account alias and domain name to retrieve the zone's DNS records.

Instructions

Get all DNS records for a specific zone/domain

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
accountYesAccount alias from accounts.json (use list_accounts to see options)
domainYesDomain name to query

Implementation Reference

  • src/tools.py:207-217 (registration)
    Tool registration (definition) for whm_dns_zone_records in the whm_tools() function. Defines name, description, and inputSchema requiring 'account' and 'domain'.
    Tool(
        name="whm_dns_zone_records",
        description="Get all DNS records for a specific zone/domain",
        inputSchema={
            "type": "object",
            "properties": {
                **ACCOUNT_PARAM,
                "domain": {"type": "string", "description": "Domain name to query"}
            },
            "required": ["account", "domain"]
        }
  • Tool handler for whm_dns_zone_records in the handle_whm_tool() function. Calls WHM API 'dumpzone' with the domain parameter.
    case "whm_dns_zone_records":
        return await _get(client, url("dumpzone"), headers, {"domain": args["domain"]})
  • Dispatcher that invokes handle_whm_tool when the tool name starts with 'whm_', routing call to the handler.
    async with httpx.AsyncClient(verify=False, timeout=30) as client:
        if name.startswith("whm_"):
            result = await handle_whm_tool(client, account, name, arguments)
  • The _get helper function used by the handler to make HTTP GET requests to the WHM API and return JSON.
    async def _get(client: httpx.AsyncClient, url: str, headers: dict, params: dict = None) -> dict:
        try:
            r = await client.get(url, headers=headers, params=params or {})
            r.raise_for_status()
            return r.json()
        except Exception as e:
            return {"error": str(e)}
Behavior2/5

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

No annotations provided; description only says 'get', implying read-only but lacks details on authentication, rate limits, or response structure.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Single sentence, front-loaded with action and resource. Efficient but could include more detail without harming conciseness.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

No output schema, no annotations, and description is too minimal for a tool with two required parameters. Lacks information on response format or usage constraints.

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% with clear parameter descriptions; description adds no extra value beyond what schema provides.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

Description clearly states it retrieves DNS records for a zone/domain, distinguishing it from sibling tool whm_dns_list_zones which lists zones.

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 guidance on when to use this tool vs alternatives like cpanel_dns_records or whm_dns_list_zones. Missing context about prerequisites.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/manofsadness/ItchWHMMCP'

If you have feedback or need assistance with the MCP directory API, please join our Discord server