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

obambu-cpanel-mcp

by RodrigueDev13
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

create_database

Create a new MySQL database on your cPanel hosting account by specifying the database name. Simplifies database provisioning for web applications.

Instructions

Create a new MySQL database.

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>"
    },
    "name": "create_database"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesDatabase name (without the cPanel account prefix)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.2

TDQS

B3.2/5.0
Behavior2/5

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

With no annotations, the description carries the full burden of behavioral disclosure. It only states that a new database is created, offering no details about side effects, permissions required, reversibility, or what happens on success. It is not misleading but is extremely minimal.

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 redundant words. It is appropriately sized for a simple tool and front-loads the core action.

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 mutation tool with no annotations and no output schema, the description is insufficiently complete. It does not explain the context of creation (e.g., under the cPanel account), the automatic prefixing mentioned in the schema, or expected return values. The sibling tools hint at a workflow, but the description alone leaves the agent without enough context.

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 coverage is 100% and the parameter 'name' has a clear description ('without the cPanel account prefix'). The tool description adds no additional parameter information, but the schema already documents the sole parameter adequately, so the baseline of 3 applies.

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 'Create a new MySQL database' uses a specific verb and resource, clearly distinguishing it from sibling tools like grant_database_privileges, create_database_user, and list_databases. It states exactly what the tool does with no ambiguity.

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 explicit guidance on when to use this tool versus alternatives. There is no mention of prerequisites, related tools (e.g., creating a user or granting privileges), or scenarios where another tool would be more appropriate. Usage is only implied by the tool's name and description.

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