ncloud-gov-mcp-server

ncloud_list_mysql_databases

Read-only

List databases in a Cloud DB for MySQL instance by supplying the Cloud MySQL instance number.

Instructions

List databases in a Cloud DB for MySQL instance

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": {
      "cloudMysqlInstanceNo": "<cloudMysqlInstanceNo>"
    },
    "name": "ncloud_list_mysql_databases"
  }
}

Input Schema

Name	Required	Description	Default
`cloudMysqlInstanceNo`	Yes	Cloud MySQL instance number

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.1Aug 2, 2026

TDQS

A3.7/5.0

Behavior2/5

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

The readOnlyHint annotation already signals a safe read operation, and the description adds no further behavioral details such as pagination behavior, response structure, or instance-existence requirements. It only restates the action without going beyond the structured information.

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?

The description is a single sentence of nine words, with no filler or redundancy. It is front-loaded and immediately communicates the tool's operation and scope.

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

Completeness5/5

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

For a simple one-parameter read-only list operation, the description sufficiently states what is listed and for which resource. The absence of an output schema is acceptable because 'List databases' clearly implies a list of database entries, and no additional complexity warrants further elaboration.

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?

The schema fully describes the single parameter cloudMysqlInstanceNo as 'Cloud MySQL instance number', and the tool description does not add any additional semantic meaning. Since schema coverage is 100%, the baseline score of 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?

The description uses the specific verb 'List' and identifies the resource as 'databases' scoped to 'a Cloud DB for MySQL instance', clearly distinguishing it from sibling tools like ncloud_list_mysql_users and ncloud_list_mysql_instances. This leaves no ambiguity about the tool's function.

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 description provides clear context that this tool enumerates the databases of a specific MySQL instance, but it does not explicitly state when to use it versus related list tools or mention any exclusions. Usage is implied rather than directly guided.

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

Deploy Server