List MySQL databases on your Combell account, showing hostname, sizes, user count, and account ID. Use it to review or inventory your databases before making changes.
List the MySQL databases on your Combell account with hostname, sizes, user count and account id.
| Name | Required | Description | Default |
|---|---|---|---|
| skip | No | Number of items to skip (default 0) | |
| take | No | Number of items to return (the API may return fewer) |
Changes observed during successful MCP inspections.
v1.0.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already cover read-only, idempotent, and non-destructive behavior. The description adds value by clarifying the account scope and the specific fields returned, which is useful since there is no output schema. It does not disclose pagination behavior, but skip/take parameters already hint at that.
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?
A single sentence that is front-loaded with the core action and resource, followed immediately by the useful return-field details. There is no redundant or filler content.
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, read-only list operation with full schema coverage and safety annotations, the description provides enough context: account scope, output fields, and the resource type. It could be slightly richer by mentioning pagination or the absence of filtering, but those are minor gaps.
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 input schema fully documents both parameters (skip and take) with descriptions, so the baseline is 3. The description adds no extra meaning about these parameters, but none is needed given the 100% schema coverage.
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'), names the exact resource ('MySQL databases on your Combell account'), and enumerates the returned information ('hostname, sizes, user count and account id'). This clearly differentiates it from sibling tools like combell_mysql_databases_get, create, and delete.
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 implies this tool is for getting an account-level overview of MySQL databases, but it does not explicitly state when to choose it over combell_mysql_databases_get or when not to use it. The intended use is inferable from 'List', but no alternative routing is provided.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.