mcp-1panel-plus

Overview Schema Source Related Servers Discussions Admin

Get MySQL Runtime Status

get_mysql_status

Read-only

Reads connection, thread, traffic, and uptime counters from a local MySQL instance on a selected node to monitor database health and activity.

Instructions

Read connection, thread, traffic, and uptime counters from a local MySQL instance on the selected node.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "database": "<database>"
    },
    "name": "get_mysql_status"
  }
}

Input Schema

Name	Required	Description	Default
`nodeId`	No	Target node ID: "local" for the Main Node, or a numeric string ID (e.g. "3") from list_nodes.	local
`database`	Yes	Local MySQL instance name.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Nov 11, 2026

TDQS

A3.8/5.0

Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare readOnlyHint=true, openWorldHint=true, and destructiveHint=false, so the safety profile is covered. The description adds value by enumerating the categories of counters returned (connection, thread, traffic, uptime), which matters because there is no output schema; it stops short of describing response shape or any per-node failure behavior.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single front-loaded sentence with the verb, the data categories, and the scope in that order; nothing is redundant or padded.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a two-parameter read-only tool with full schema coverage and annotations, the definition covers what is read and where. The one residual gap is that it says nothing about the shape of the returned counters, which the absence of an output schema leaves partly undocumented.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, with nodeId and database both documented in the schema, so the baseline is 3. The description echoes the semantics ("local MySQL instance" for database, "selected node" for nodeId) but adds no format, validation, or defaulting detail beyond what the schema already states.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description pairs a specific verb ("Read") with a precise resource ("connection, thread, traffic, and uptime counters") and scopes it to "a local MySQL instance on the selected node." That clearly separates it from inventory-oriented siblings like list_mysql_instances, 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.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is only implied by the verb "Read" and the status-counter subject; there is no explicit statement of when to call this instead of list_mysql_instances or when it would be inappropriate. Adequate for an obvious read tool, but leaves routing to inference.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.