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

ncloud-gov-mcp-server

by sjk4425
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

ncloud_get_root_password

Read-only

Retrieve the root password for a server instance using its instance number and an optional private key for decryption.

Instructions

Get the root password for a server 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": {
      "serverInstanceNo": "<serverInstanceNo>"
    },
    "name": "ncloud_get_root_password"
  }
}

Input Schema

NameRequiredDescriptionDefault
privateKeyNoPrivate key to decrypt the password
serverInstanceNoYesServer instance number

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

B3.2/5.0
Behavior2/5

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

Annotations declare readOnlyHint=true, and the description does not contradict this. However, the description fails to disclose that the returned password is typically encrypted and requires the privateKey parameter to decrypt—a key behavioral aspect not covered by the annotations.

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, clear sentence that immediately conveys the core function. There is no wasted text or repetition of schema information.

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

Completeness2/5

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

Given the sensitive nature of retrieving a root password, the description omits important context such as the encryption/decryption flow and the optional nature of the private key (serverInstanceNo is required, privateKey is not). The schema partly covers this, but the tool's overall context remains incomplete for an agent to use it confidently.

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%, so the input schema already documents both parameters meaningfully (e.g., privateKey is 'Private key to decrypt the password'). The description adds no extra parameter detail, so a baseline score 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 tool retrieves the root password for a specific server instance. The singular 'a server instance' distinguishes it from the sibling tool ncloud_get_root_password_list, which handles multiple instances.

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 gives no guidance on when to use this tool versus the list variant or any other alternative. It also doesn't mention prerequisites such as needing the private key to decrypt the password, which is critical for successful use.

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