cPanel MCP Server

create_postgresql_user

Create a new PostgreSQL user with a specified username and password for database access on cPanel.

Instructions

Create a new PostgreSQL user

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": {
      "name": "<name>",
      "password": "<password>"
    },
    "name": "create_postgresql_user"
  }
}

Input Schema

Name	Required	Description	Default
`name`	Yes	Username
`password`	Yes	Password

Schema Changelog

Changes observed during successful MCP inspections.

First observedv2.0.0Aug 6, 2026

TDQS

B3.2/5.0

Behavior2/5

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

No annotations are provided, so the description must carry the full burden of behavioral disclosure. It only restates the action without mentioning requirements, failure conditions, permissions, or side effects. For a creation tool, there is no disclosure about duplicate users or privilege implications.

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 succinct sentence that directly states the tool's purpose. It is extremely concise and contains no filler, though it may be too sparse for other dimensions.

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?

Given the large number of sibling database tools and no output schema, the description lacks sufficient context for an agent to fully understand the tool's behavior and distinguish it from similar creation tools. It does not explain return values, idempotency, or operational requirements, which is a gap for a simple but context-dependent operation.

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 input schema already fully describes both parameters (name as 'Username', password as 'Password'), and the description adds no additional semantic context. Per rubric, schema coverage is 100%, so a baseline of 3 is appropriate.

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 ('Create') and a clear resource ('PostgreSQL user'), which clearly differentiates it from sibling tools like create_mysql_user or create_postgresql_database. It unambiguously states the tool's action.

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?

The description provides no guidance on when to use this tool versus alternatives such as create_mysql_user or set_postgresql_privileges. There is no mention of prerequisites, scenarios, or exclusions.

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

Deploy Server