Skip to main content
Glama
Sign In
cPanel MCP Server

cPanel MCP Server

by 0xHayd3n
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

get_dns_records

Retrieve complete DNS records for any domain to inspect zone settings and troubleshoot DNS configuration.

Instructions

Get all DNS records for a zone/domain

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": {
      "domain": "<domain>"
    },
    "name": "get_dns_records"
  }
}

Input Schema

NameRequiredDescriptionDefault
domainYesDomain name to get records for

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0

TDQS

B3.3/5.0
Behavior2/5

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

No annotations are provided, so the description carries full burden. It only states 'Get all DNS records for a zone/domain' and does not disclose potential mutation, rate limits, pagination, required permissions, or error behavior. The 'get' verb implies read-only, but this is not explicit.

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 concise sentence with no filler. 'Get all DNS records for a zone/domain' is front-loaded with the action and resource, achieving high efficiency.

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 one-parameter read tool, the description is minimally sufficient for invocation. However, it lacks context on return format, edge cases, or how to differentiate from get_dnssec_ds_records, and the absence of annotations leaves safety assumptions unverified.

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 only parameter, 'domain', has full schema description coverage (100%) with 'Domain name to get records for'. The tool description adds no extra meaning beyond the schema, matching the baseline score of 3 for adequate schema coverage.

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 retrieves all DNS records for a zone/domain, using a specific verb ('get') and resource ('all DNS records'). It distinguishes itself from sibling tools like add/edit/delete_dns_record (mutations) and get_dnssec_ds_records (specific record type).

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 is provided on when to use this tool versus alternatives. The description does not mention exclusions, such as using get_dnssec_ds_records for DS records, or frame this as the primary read-only list tool among DNS operations.

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

Deploy Server

Other Tools