Assign MySQL privileges to a user on a specific database, letting you grant full or comma-separated access rights from your cPanel hosting environment.
Set privileges for a MySQL user on a database
| Name | Required | Description | Default |
|---|---|---|---|
| user | Yes | Full MySQL username | |
| database | Yes | Full database name | |
| privileges | No | Comma-separated privileges or ALL PRIVILEGES | ALL PRIVILEGES |
Changes observed during successful MCP inspections.
v2.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the full burden for behavioral disclosure. It only states a generic 'set' operation without explaining whether it replaces existing privileges, requires specific permissions, or has side effects such as revoking grants not listed.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single concise sentence that gets straight to the point. It is appropriately minimal for a simple tool and contains no filler.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
The tool is a mutation with no annotations or output schema, yet the description provides no information about behavior, prerequisites, or return values. It fails to clarify whether 'set' means granting, replacing, or merging privileges, which is essential for correct invocation.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
All three parameters are described in the schema with complete coverage. The description itself adds no additional meaning beyond the action, so it doesn't augment the schema's own parameter descriptions.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description specifies a clear action ('set privileges') on a specific resource (MySQL user on a database), and the MySQL qualifier distinguishes it from Postgres equivalents. The sibling revoke_mysql_privileges further disambiguates the intent.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
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. It is implicitly the counterpart to revoke_mysql_privileges, but no context or conditions for use are stated.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.