ncloud-mcp-server

ncloud_hadoop_list_mysql_users

Read-only

List MySQL users for Hive metastore integration, providing the account information needed to configure or troubleshoot the Hive metastore on Cloud DB for MySQL.

Instructions

List MySQL users for Hive metastore integration

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_hadoop_list_mysql_users"
  }
}

Input Schema

Name	Required	Description	Default
`regionCode`	No	Region code
`cloudMysqlInstanceNo`	Yes	Cloud DB for MySQL instance number

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.10.1Jul 29, 2026

TDQS

A3.8/5.0

Behavior3/5

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

Annotations include readOnlyHint=true, which is consistent with the description. The description does not disclose any additional behavioral traits such as filtering behavior, pagination, or the specific set of users returned. It adds no behavioral context beyond what annotations already guarantee, but it does not contradict them.

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 concise sentence with no superfluous words. It front-loads the verb and resource, making it easy to parse quickly.

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 simple read-only list operation with well-documented parameters and annotations, the description is mostly sufficient. However, it lacks any detail about the response format or how the listed users relate to the Hive metastore configuration workflow, which would improve completeness.

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%: both parameters ('regionCode' and 'cloudMysqlInstanceNo') have clear descriptions. The tool description adds no additional meaning to the parameters, so 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 a specific verb (List) and resource (MySQL users) with a clear qualifier 'for Hive metastore integration', which distinguishes it from the general 'ncloud_list_mysql_users' tool and sibling Hadoop tools like 'ncloud_hadoop_list_mysql_instances'. The purpose is immediately clear.

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 implies usage context ('for Hive metastore integration') but does not explicitly state when to use this tool versus alternatives, nor does it provide any exclusions or mention of sibling tools like test_hive_metastore or save_hive_metastore. The context is helpful but not actionable as guidance.

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

Deploy Server