Skip to main content
Glama
Sign In
obambu-cpanel-mcp

obambu-cpanel-mcp

by RodrigueDev13
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

list_dns_records

Retrieve DNS zone records for any domain to review its current configuration.

Instructions

List DNS zone records 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": {
      "zone": "<zone>"
    },
    "name": "list_dns_records"
  }
}

Input Schema

NameRequiredDescriptionDefault
zoneYesDomain name whose DNS zone to read, e.g. example.com

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.2

TDQS

A3.8/5.0
Behavior3/5

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

No annotations are present, so the description must carry the transparency burden. The verb 'List' implies a read-only operation, which is a useful behavioral signal, but the description does not disclose output format, pagination, error responses, or authentication requirements. It adds minimal context beyond the tool name.

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 unnecessary words or repetition. Every word adds value, making it highly efficient.

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 simple list tool with one well-documented parameter, the description is largely complete. It doesn't describe return format or error behavior, but the absence of an output schema and the tool's straightforward nature make this acceptable. The description adequately covers the tool's primary use case.

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 covers 100% of the parameter with a clear description ('Domain name whose DNS zone to read, e.g. example.com'). The tool description adds no additional parameter semantics, so the baseline score of 3 is appropriate given the 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 'List' with a clear resource 'DNS zone records' and scoping 'for a domain'. This unambiguously distinguishes it from sibling tools like add_dns_record, edit_dns_record, remove_dns_record, and list_domains.

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 for reading DNS records but does not explicitly state when to use it versus alternatives, nor does it mention when not to use it. The context is clear enough that an agent could infer its purpose, but no exclusionary or alternative guidance is provided.

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