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

obambu-cpanel-mcp

by RodrigueDev13
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

grant_database_privileges

Grant database privileges to a user for a specific database, with options to set custom permissions.

Instructions

Grant a database user privileges on a 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": {
      "user": "<user>",
      "database": "<database>"
    },
    "name": "grant_database_privileges"
  }
}

Input Schema

NameRequiredDescriptionDefault
userYesFull database username (as returned by list_database_users)
databaseYesFull database name (as returned by list_databases)
privilegesNoComma-separated privileges, defaults to ALL PRIVILEGESALL PRIVILEGES

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.2

TDQS

B3.3/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 disclose behavioral traits. It only states 'Grant... privileges' with no mention of side effects, whether existing privileges are replaced, permission requirements, or return behavior. This is inadequate for a mutation tool.

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, front-loaded sentence with no redundant words. It is appropriately sized for the tool's simplicity.

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 tool is simple and the schema covers parameter semantics, but the description omits important behavioral context such as whether privileges are additive or replacing, and does not mention output or failure modes. The tool is minimally complete but has clear gaps.

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 provides 100% coverage with useful descriptions for all parameters, including the comma-separated format and default for privileges. The description adds no additional parameter semantics, but the schema does the heavy lifting, yielding the baseline score of 3.

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 the specific verb 'Grant' and identifies the resource ('privileges on a database'), making the action and target unambiguous. It is clearly distinct from sibling tools like create_database_user or create_database.

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, nor prerequisites or exclusions. The purpose implies a use case, but explicit usage context is missing.

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