Retrieve your MySQL server version, database name, charset, timezone, and safety limits to verify connection settings before running read-only queries.
Return the configured MySQL database, server version, charset, timezone, and safety limits.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections.
v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description must disclose behavioral traits. The verb 'Return' implies a read-only, side-effect-free operation, but the description does not explicitly confirm this, nor does it mention authentication requirements, rate limits, or whether any server state is affected.
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, front-loaded sentence that lists the returned fields without waste. Every element earns its place.
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 no-argument read tool with no output schema, the description enumerates the key return values (database, version, charset, timezone, safety limits), which is sufficient for an agent to understand the tool's output. It could additionally state that no arguments are needed, but the schema already conveys that.
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?
With zero parameters and complete schema coverage, the description need not discuss parameters. The baseline of 4 applies because no parameter information is missing.
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 specific verb ('Return') and enumerates the exact server-level resources (database, version, charset, timezone, safety limits). This clearly differentiates it from sibling tools that deal with tables, indexes, queries, or execution plans, though no sibling is named explicitly.
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?
Provides no guidance on when to call this tool versus alternatives, no prerequisites, and no exclusions. It only describes what the tool returns, leaving the agent to infer that it is used for server configuration inspection.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.