Skip to main content
Glama

cpanel_uapi

Execute official cPanel UAPI module functions—Mysql, Cron, SSL, SubDomain, Email—to manage hosting tasks directly from AI clients without SSH or server scripts.

Instructions

Execute any official cPanel UAPI module function (e.g., Mysql, Cron, SSL, SubDomain, Email).

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": {
      "module": "<module>",
      "func": "<func>"
    },
    "name": "cpanel_uapi"
  }
}

Input Schema

NameRequiredDescriptionDefault
funcYescPanel UAPI function name (e.g., list_databases, list_cron).
moduleYescPanel UAPI module name (e.g., Mysql, Cron, SSL).
paramsNoOptional key-value query parameters.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full burden. It discloses only that it executes functions; it does not explain that side effects, permissions, return shapes, authentication, rate limits, and error behavior depend entirely on the chosen module/function.

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?

A single front-loaded sentence with no filler. It is concise and structurally clear, even though brevity contributes to the completeness gap rather than conciseness being the problem.

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?

For a generic arbitrary-execution tool with no annotations and no output schema, the definition is too thin. It does not describe authorization context, whether calls are read-only or destructive, how errors surface, or how to determine valid module/function pairs.

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 description coverage is 100%, including clear descriptions for module, func, and params. The description adds only examples of modules, which duplicate the schema's examples, and does not explain params serialization or any constraints beyond the schema.

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?

States a specific verb ('Execute') and resource ('cPanel UAPI module function'), with module examples. It is clearly distinct from the filesystem-oriented siblings, though the generic 'any' scope leaves the supported function subset implicit.

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?

Provides no when-to-use guidance, exclusions, or prerequisites. An agent cannot tell from the description when this generic dispatcher should be used versus a dedicated cPanel module tool, or what must be validated before calling.

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