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

ncloud-gov-mcp-server

by sjk4425
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

ncloud_nks_update_secret_encryption

Idempotent

Update secret encryption for an NKS cluster by providing the cluster UUID and KMS key tag, ensuring sensitive data is protected with your chosen key.

Instructions

Configure secret encryption for an NKS 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": {
      "clusterUuid": "<clusterUuid>"
    },
    "name": "ncloud_nks_update_secret_encryption"
  }
}

Input Schema

NameRequiredDescriptionDefault
kmsKeyTagNoKMS key tag for secret encryption
clusterUuidYesUUID of the cluster

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

B3.3/5.0
Behavior2/5

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

There is no annotation contradiction; idempotentHint and destructiveHint are consistent with a non-destructive configuration update. However, the description adds no behavioral context beyond the annotations—it doesn't describe effects on existing encryption settings, cluster state requirements, or what happens if kmsKeyTag is omitted.

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 that states the core purpose. It is front-loaded and contains no redundant information.

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?

Given the low complexity (2 params, no output schema) and existing annotations/schema coverage, the description is minimally adequate. However, it leaves ambiguity about the optional kmsKeyTag param and the exact behavior of 'configure' (e.g., enable, update, or disable encryption), so it is not fully complete.

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 input schema provides full descriptions for both parameters (clusterUuid and kmsKeyTag), so the baseline is 3. The description adds no additional meaning about how the parameters interact or optionality, relying entirely on the schema.

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 ('Configure') and the resource ('secret encryption for an NKS cluster'). It distinguishes from sibling tools like ncloud_nks_update_auth_type or ncloud_nks_set_oidc because no other tool targets secret encryption. The verb and object are specific and unambiguous.

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, nor any prerequisites or exclusions. It solely states what it does without context, leaving the agent to infer usage.

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