aapanel-mcp

Reset the MySQL root password

danger_mysql_reset_root_password

Destructive

Reset the MySQL root password to regain access, but all existing root logins, cron jobs, and monitoring agents using the old password will break.

Instructions

Set a new MySQL root password. Every existing root login, cron job and monitoring agent that used the old password will stop working.

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": {
      "password": "<password>"
    },
    "name": "danger_mysql_reset_root_password"
  }
}

Input Schema

Name	Required	Description	Default
`password`	Yes	New MySQL root password.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.1-alpha.0Sep 29, 2026

TDQS

A3.8/5.0

Behavior4/5

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

Annotations already declare destructiveHint=true and idempotentHint=false, so the safety profile is known. The description adds concrete blast radius beyond that: existing root logins, cron jobs and monitoring agents break. It still doesn't mention required permissions or whether the change is reversible.

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?

Two short sentences, zero waste. The action is front-loaded and the consequence follows immediately, and every sentence earns its place.

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 single-parameter destructive tool with no output schema and annotations covering the mutation profile, the description covers action plus impact. It stops short of auth/prerequisite context an operator would want before running a root credential change.

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?

Only one parameter with 100% schema description coverage, so the schema already documents the password field. The description adds no syntax, format, or constraint details beyond it; baseline 3 applies.

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

Purpose5/5

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

States a specific verb+resource: 'Set a new MySQL root password.' The word 'root' distinguishes it from the sibling db_set_password, which handles ordinary database users, so an agent can route correctly without opening the schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

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

The description states what happens but never says when to use this versus db_set_password or danger_mysql_root_password's alternatives, nor what preconditions must hold. There is no explicit when-to-use or when-not-to-use guidance.

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

Deploy Server