List databases in legacy MySQL servers with SHOW DATABASES, hiding system databases by default. Use it to inspect available schemas without write operations.
Lists databases using SHOW DATABASES. System databases are hidden by default according to MYSQL_LEGACY_HIDE_SYSTEM_DATABASES.
| Name | Required | Description | Default |
|---|---|---|---|
| include_system_databases | No | Overrides MYSQL_LEGACY_HIDE_SYSTEM_DATABASES for this call. |
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description carries the behavioral disclosure burden. It discloses a key behavior beyond the name: system databases are hidden by default based on MYSQL_LEGACY_HIDE_SYSTEM_DATABASES. This gives useful context about filtering behavior, though it does not explicitly state read-only semantics or output shape.
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?
Two short sentences with no filler. The core operation is front-loaded, followed by the important default-filtering behavior. Every sentence contributes meaningful information.
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 simple optional-boolean list tool, the description is largely complete: it names the operation, the SQL method, and the default behavior. The lack of an output schema is not a major issue since listing databases implies returning database names, but explicit mention of response format would make it fully complete.
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?
The single parameter is fully documented in the schema, so schema description coverage is 100%. The description does not need to re-explain the parameter, but it also does not add extra semantic value beyond what the schema already provides. Baseline 3 is appropriate.
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 clearly states the operation: 'Lists databases using SHOW DATABASES.' It names a specific verb, resource, and even the underlying MySQL command. The resource 'databases' inherently distinguishes it from sibling tools like mysql_legacy_list_tables.
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?
Usage is implied by the verb and resource: use this when you need to list databases. However, there is no explicit guidance about when to prefer this tool over alternatives, nor any mention of exclusions or prerequisites. The description does not route users away from sibling tools.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.