Skip to main content
Glama
Sign In
mcp-1panel-plus

mcp-1panel-plus

by EC061
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

List MySQL Databases

list_databases
Read-only

Lists databases in an explicitly named local MySQL instance on a selected node; passwords are not returned.

Instructions

List databases inside an explicitly named local MySQL instance on the selected node. Passwords are never returned.

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": "list_databases"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNo1-indexed page number.
nodeIdNoTarget node ID: "local" for the Main Node, or a numeric string ID (e.g. "3") from list_nodes.local
databaseYesLocal MySQL instance name (from `list_mysql_instances`).
page_sizeNoItems per page (1-500).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so safety is established. The description adds one genuinely new behavioral fact, that passwords are never returned, but says nothing about pagination shape, empty results, or connection failures for a remote MySQL instance.

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, with the scope constraint front-loaded and no filler wording. Every clause carries information.

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 four-parameter read-only list tool with full schema coverage and annotations, the definition covers scope, prerequisite naming, node targeting and the no-password guarantee. The gap is minor: nothing about ordering or how paginated totals are surfaced, though there is no output schema to lean on.

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 coverage is 100%, so page, page_size, nodeId and database are already documented in the schema, including the 'from list_mysql_instances' hint for the database parameter. The description only reinforces that the instance must be named and the node selected, adding no syntax or format detail beyond the schema.

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?

States a specific verb and resource (list databases) and constrains scope to a named local MySQL instance on a node, which separates it from list_mysql_instances (instances, not databases) and from list_postgresql_databases by engine. It never names a sibling alternative explicitly, so it stops short of a 5.

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?

The phrase 'explicitly named local MySQL instance' implies the caller must already know an instance name rather than discovering databases generically, which is useful context. There is no explicit when-to-use/when-not statement and no pointer to a sibling for the case where the instance name is unknown.

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

Deploy Server

Other Tools