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

ncloud-mcp-server

by sjk4425
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

ncloud_kms_cancel_key_deletion

Idempotent

Cancel a pending key deletion request for a key in REVOKE state. Use the key's keyTag to stop scheduled removal and retain access to the key.

Instructions

Cancel a pending key deletion request. Only keys in REVOKE state can be cancelled.

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_cancel_key_deletion"
  }
}

Input Schema

NameRequiredDescriptionDefault
keyTagYesKey tag - unique identifier derived from key name

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.10.1

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare idempotentHint=true and destructiveHint=false. The description adds valuable behavioral context beyond annotations by specifying the REVOKE state requirement and the nature of the operation (cancelling a pending request). This helps the agent understand the key lifecycle implications without contradicting 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 two sentences long and front-loads the action immediately. Every word earns its place, with no filler or redundancy.

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

Completeness5/5

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

This is a simple tool with one parameter and no output schema. The annotations cover idempotency and non-destructiveness, and the description covers the key state requirement. Together, this is fully complete for an agent to use the tool correctly.

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 has 100% description coverage for the single parameter keyTag, so the schema already documents it. The description does not add any additional parameter meaning beyond what the schema provides, so a 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 verb 'Cancel' and the resource 'pending key deletion request', and adds a specific precondition ('Only keys in REVOKE state'). This distinguishes it from siblings like ncloud_kms_request_key_deletion and ncloud_kms_delete_key.

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 a clear context for use: only keys in REVOKE state can be cancelled. This implies the tool should be used when a deletion request is pending and the key is in the REVOKE state. It doesn't explicitly name alternatives, but the state requirement is a strong usage guideline.

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