ncloud-gov-mcp-server

ncloud_kms_reencrypt

Re-encrypt ciphertext with the latest master key version after key rotation to keep data decryptable. Supports AES256 and RSA2048 key types.

Instructions

Re-encrypt ciphertext with the latest version of the specified master key. Used after key rotation to update encrypted data. Only AES256 or RSA2048 key types supported.

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": {
      "keyTag": "<keyTag>",
      "ciphertext": "<ciphertext>"
    },
    "name": "ncloud_kms_reencrypt"
  }
}

Input Schema

Name	Required	Description
`keyTag`	Yes	Key tag - unique identifier derived from key name
`context`	No	Base64-encoded context for convergent encryption
`ciphertext`	Yes	Ciphertext to re-encrypt (string or array of strings)

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.1Aug 2, 2026

TDQS

A3.9/5.0

Behavior3/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 usefully discloses that only AES256 or RSA2048 key types are supported and that re-encryption uses the latest key version. However, it does not disclose the output format, whether the original ciphertext is replaced or returned, or any side effects such as requiring certain permissions. This leaves important behavioral details unstated.

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 three short sentences, front-loaded with the primary action. Every sentence adds relevant information (what it does, when to use, constraints), with no filler or redundancy.

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?

For a tool with no output schema and no annotations, the description covers the core purpose and a key constraint (supported key types) but omits the return behavior. It does not explain what the tool returns (e.g., new ciphertext) or how the 'context' parameter affects the operation, leaving gaps for an agent unfamiliar with KMS. It is adequate but 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 already provides complete descriptions for all three parameters (keyTag, context, ciphertext), including that ciphertext can be a string or array. The tool description adds no parameter-specific detail beyond what the schema provides, so it meets the baseline for high schema coverage but does not go beyond it.

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 a specific verb ('Re-encrypt') and resource ('ciphertext with the latest version of the specified master key'), making the tool's function unambiguous. It also distinguishes itself from related KMS siblings like ncloud_kms_encrypt and ncloud_kms_decrypt by focusing on re-encryption after key rotation.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description explicitly provides a use case: 'Used after key rotation to update encrypted data.' This gives clear context for when to invoke the tool. It does not explicitly list exclusions or alternatives, but the stated purpose is sufficient for an agent to select it appropriately among the many KMS operations.

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

Deploy Server