ncloud-gov-mcp-server

ncloud_kms_delete_key

DestructiveIdempotent

Permanently delete a KMS key. Requires key in REVOKE state and confirm=true for this irreversible action.

Instructions

⚠️ Destructive: Permanently delete a KMS key. This action is irreversible. The key must be in REVOKE state (deletion requested) before it can be permanently deleted. Set confirm=true to execute.

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>"
    },
    "name": "ncloud_kms_delete_key"
  }
}

Input Schema

Name	Required	Description	Default
`keyTag`	Yes	Key tag - unique identifier derived from key name (required)
`confirm`	No	Must be true to actually execute the destructive operation

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.1Aug 2, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already declare destructiveHint=true and idempotentHint=true, but the description adds valuable context: it's irreversible, requires the key to be in REVOKE state, and requires a confirm flag. This goes beyond the annotation's simple destructive flag and provides operational detail. No contradiction with 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 two sentences, front-loaded with a warning emoji, and contains no fluff. Every sentence provides necessary safety or usage 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?

Given two parameters, no output schema, and annotations covering destructiveness, the description covers the essential safety preconditions and execution requirement. It could mention what happens if the key is not in REVOKE state, but this is not critical for correct invocation.

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 coverage is 100%, so the schema already documents both keyTag and confirm thoroughly. The description adds a slight reinforcement that confirm=true actually executes the operation, but this largely mirrors the schema description for confirm. It does not add new meaning for keyTag beyond what's in 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 states a specific verb and resource: 'Permanently delete a KMS key.' This clearly distinguishes it from sibling tools like ncloud_kms_request_key_deletion (which requests deletion) and ncloud_kms_cancel_key_deletion (which cancels a request).

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 provides explicit context for when to use this tool: 'The key must be in REVOKE state (deletion requested) before it can be permanently deleted.' It also instructs the user to 'Set confirm=true to execute,' which is a clear usage requirement. It doesn't name alternatives explicitly but the state precondition implies the appropriate sequence.

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

Deploy Server