Skip to main content
Glama
Sign In
cPanel MCP Server

cPanel MCP Server

by 0xHayd3n
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

export_dnssec_key

Export the DNSSEC DNSKEY record for a domain to configure DNSSEC settings or share with your DNS provider.

Instructions

Export a DNSSEC DNSKEY record for a 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": "export_dnssec_key"
  }
}

Input Schema

NameRequiredDescriptionDefault
domainYesDomain name

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0

TDQS

A3.5/5.0
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It says 'Export', which implies a read-only operation, but it does not state side effects (e.g., whether it is non-destructive), whether DNSSEC must be enabled, or what the output format is. This lack of detail is a notable gap.

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, well-structured sentence that states the action and object clearly. Every word earns its place, with no verbose or redundant content.

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/export tool, the description states the core purpose adequately. However, it omits details such as the expected return value (the DNSKEY record format) and any prerequisites (e.g., DNSSEC enabled on the domain), which would be useful for a fully self-contained description.

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 schema has one parameter ('domain') with 100% description coverage, so the schema already documents it. The description adds no additional semantic info about the parameter (e.g., domain format or required type), meeting the baseline for high 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 uses a specific verb ('Export') and resource ('DNSSEC DNSKEY record') with a clear scope ('for a domain'). It distinguishes itself from sibling tools like get_dnssec_ds_records or add_dns_record, which deal with different DNS records or operations.

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 description implies usage: when you need a DNSKEY record for a domain, use this tool. However, it offers no explicit guidance on when not to use it, nor does it mention alternatives such as get_dnssec_ds_records, which might be more appropriate for DS records.

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