Skip to main content
Glama
Sign In
ncloud-gov-mcp-server

ncloud-gov-mcp-server

by sjk4425
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

ncloud_cdss_reset_cmak_password

Reset the CMAK access account password for a CDSS cluster by specifying the cluster instance number and new password.

Instructions

Reset CMAK access account password for a CDSS cluster

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": {
      "serviceGroupInstanceNo": "<serviceGroupInstanceNo>",
      "kafkaManagerUserPassword": "<kafkaManagerUserPassword>"
    },
    "name": "ncloud_cdss_reset_cmak_password"
  }
}

Input Schema

NameRequiredDescriptionDefault
serviceGroupInstanceNoYesCluster instance number
kafkaManagerUserPasswordYesNew CMAK password (8-20 chars, letters+numbers+special)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

A3.5/5.0
Behavior2/5

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

Annotations are empty, so the description carries the full burden. It only says 'reset' with no disclosure of side effects, whether the cluster will be interrupted, if a rolling restart is required, or if the existing session is invalidated. For a mutating action on a cluster, this is insufficient transparency.

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. It is concise with no filler or redundant information, matching the ideal length for a simple reset operation.

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

Completeness3/5

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

There is no output schema, and the description does not explain return behavior, expected confirmation, or whether the reset causes temporary unavailability. However, with only 2 well-documented parameters and a straightforward operation, the description is minimally sufficient but could benefit from context about post-reset effects or prerequisites.

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 both parameters already described ('Cluster instance number' and 'New CMAK password (8-20 chars, letters+numbers+special)'). The description itself does not add further parameter meaning beyond what the schema provides, so 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 ('Reset'), the target resource ('CMAK access account password'), and the scope ('for a CDSS cluster'). It uses a specific verb and distinguishes this from sibling tools like ncloud_cdss_restart_cmak and other CDSS management operations.

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 the tool is used when a CDSS cluster's CMAK password needs resetting, but it does not explicitly state when to use it vs alternatives, nor does it mention any prerequisites or exclusions. The context is clear from the name but lacks explicit guidance.

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