Retrieve a MySQL user's privileges for a specific database by entering the database name and username. Use this to verify access rights and troubleshoot permission issues.
List a MySQL user's privileges on a database.
| Name | Required | Description | Default |
|---|---|---|---|
| db_name | Yes | ||
| db_username | Yes |
Changes observed during successful MCP inspections.
v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the full burden of behavioral disclosure. The verb 'List' reasonably implies a read-only operation, but the description does not clarify return format, what happens if the user or database does not exist, or whether any special privileges are required to view the list.
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 focused sentence with no wasted words. It front-loads the action and resource, making it immediately scannable.
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 simple with only two required parameters, so the description conveys the core invocation clearly. However, without an output schema or annotations, it leaves the return value, error cases, and any permission-related caveats unspecified.
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?
Schema description coverage is 0%, so the description must compensate. It does map the two parameters to concepts ('user' and 'database'), and the parameter names are self-explanatory, but it adds no detail about expected formats, existence requirements, or the meaning of the returned privileges.
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 uses a specific verb ('List') and a precise resource ('a MySQL user's privileges on a database'). It clearly distinguishes this tool from related siblings like ecp_mysql_grant_privileges, ecp_mysql_revoke_privileges, and the equivalent PostgreSQL/MSSQL privilege listers.
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 guidance on when to use this tool versus alternatives. It does not mention that this is a read-only counterpart to grant/revoke, nor does it distinguish when to choose MySQL over MSSQL or PostgreSQL variants.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.