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

obambu-cpanel-mcp

by RodrigueDev13
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

list_domains

Lists all domains, subdomains, addon domains, and parked domains on a cPanel account, providing a comprehensive overview of hosted domain names.

Instructions

List all domains, subdomains, addon domains and parked domains on the account.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_domains"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.2

TDQS

A3.9/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It indicates the scope (all domains) and context (account), but does not explicitly state that this is a read-only operation or describe the response format. The verb 'list' implies read-only, but more detail on behavior (e.g., no pagination, returns array) would be beneficial.

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?

One sentence, 15 words, listing all relevant domain types without redundancy. It is concise and front-loaded, with every word adding value.

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?

The description tells you what is returned (domains, subdomains, etc.) but not the response structure or any potential limitations (e.g., whether it includes the main domain). For a simple list tool, it is adequate but has gaps in return format and edge cases.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema has zero parameters, so the description does not need to explain any. It fully covers the operation's scope without needing parameter details, aligning with the baseline for no-parameter tools.

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 action (list) and the resource (domains of various types) with specific detail (subdomains, addon, parked). It distinguishes from sibling tools like list_databases or list_dns_records, as it is the only domain-focused list tool.

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?

No explicit when-to-use or alternative tools are mentioned, but the purpose is self-evident for a list operation. The context that it lists all domains on the account is clear, yet there is no guidance on when not to use it or how it compares to other list tools.

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