ncloud-mcp-server

ncloud_change_mysql_users

Idempotent

Change MySQL DB user permissions, password, and host IP for a Cloud DB for MySQL instance. Specify the instance and user list to update access.

Instructions

Change DB user information (authority, password, hostIp) for 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>",
      "cloudMysqlUserList": "<cloudMysqlUserList>"
    },
    "name": "ncloud_change_mysql_users"
  }
}

Input Schema

Name	Required	Description
`regionCode`	No	Region code (default: first region)
`cloudMysqlUserList`	Yes	List of users to modify
`cloudMysqlInstanceNo`	Yes	Cloud MySQL instance number

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.10.1Jul 29, 2026

TDQS

A3.6/5.0

Behavior3/5

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

Annotations declare idempotentHint=true and destructiveHint=false, matching the non-destructive modify behavior described. The description adds no extra behavioral context beyond the annotations, such as side effects or permission requirements, but 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, front-loaded sentence that directly states the purpose. There is no redundant or filler 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?

Although the description is brief, it is sufficient given the rich schema and annotations. The schema covers all parameter details, and annotations clarify idempotency and non-destructive behavior. No output schema exists, so return values need not be explained.

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 detailed descriptions for all parameters including password rules, authority enum meanings, and hostIp formats. The tool description itself adds little beyond what the schema already provides, so the baseline of 3 is appropriate.

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 clearly states the action ('Change') and the resource ('DB user information ... for a Cloud DB for MySQL instance'). It names the specific fields (authority, password, hostIp) and distinguishes itself from sibling tools like add/delete/list MySQL users.

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 provides no guidance on when to use this tool versus alternatives such as ncloud_add_mysql_users or ncloud_delete_mysql_users. It does not mention prerequisites or scenarios where this tool is preferred.

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

Deploy Server