Lists all MySQL databases for a specified user. Provide the username to retrieve the complete database list.
List all MySQL databases for a specific user
| Name | Required | Description | Default |
|---|---|---|---|
| user | Yes | Username of the account to list MySQL databases for |
Changes observed during successful MCP inspections.
v1.0.1Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full burden. It doesn't disclose whether this requires admin privileges, how many results are returned, pagination, error behavior for nonexistent users, or the return format. For a list tool with zero annotation coverage, this is a significant behavioral gap.
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?
One sentence, front-loaded with the action and resource, zero waste. Perfectly sized for a simple list tool.
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?
For a 1-param list tool with no output schema and no annotations, the description is minimally adequate. It tells what the tool does but omits return format, permissions, and usage context. More context would improve completeness without violating conciseness requirements.
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 coverage is 100%, so the schema already documents the single 'user' parameter with a clear description. The description adds no further parameter meaning or format details. Baseline 3 is appropriate when schema does the heavy lifting.
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?
States a clear verb+resource: list MySQL databases, scoped to a specific user. This distinguishes it from most siblings (ftp, account, autossl), though the description doesn't explicitly differentiate from a hypothetical list-all-databases tool. Still, the purpose is unambiguous.
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?
No guidance on when to use this tool versus alternatives, no prerequisites, no mention of what the 'user' should be (system account username). The description provides no usage context beyond the implied action.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.