Retrieve MySQL/MariaDB SHOW GLOBAL STATUS counters with optional name or target filters to inspect server health and performance.
[READ] Global status counters (SHOW GLOBAL STATUS).
Args: pattern: Optional substring to filter counter names (e.g. 'Threads', 'Innodb_buffer_pool'). target: Target name from config; omit for the default.
| Name | Required | Description | Default |
|---|---|---|---|
| target | No | ||
| pattern | No |
Changes observed during successful MCP inspections.
v0.5.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The readOnlyHint=true annotation already establishes the safe-read profile, and the description's '[READ]' prefix merely restates it. Nothing beyond the annotation is added: no output volume, no cost, no note on whether counters are cumulative or per-connection.
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 purpose is front-loaded in a single bracketed sentence, followed by a compact Args block with no filler. Every line 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 zero-required-parameter read tool with no output schema, the description covers both parameters and the operation's scope. Nothing essential is missing, though return shape is left to the reader since no output schema exists.
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 carries the burden and largely does: it explains that pattern is an optional substring filter on counter names with concrete examples, and that target names a config target with omission meaning the default. Only the target-name source/format is left slightly vague.
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+resource: reads global status counters via SHOW GLOBAL STATUS. It is distinguishable in practice from siblings like show_variables and table_status, though the description does not explicitly name or contrast those alternatives.
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 read tag and the optional pattern/target parameters rather than stated. There is no explicit guidance on when to reach for this versus show_variables, table_status, or connection_stats.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.