ncloud-gov-mcp-server

ncloud_kms_get_key_info

Read-only

Retrieve detailed metadata for a KMS key by its unique key tag. Get key status, creation details, and encryption context to manage government cloud security.

Instructions

Get detailed information about a specific KMS key by its keyTag.

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

Input Schema

Name	Required	Description	Default
`keyTag`	Yes	Key tag - unique identifier derived from key name

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.1Aug 2, 2026

TDQS

A3.8/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true, signaling a safe read operation. The description adds that the tool returns 'detailed information' for one key, but does not elaborate on the exact data returned, permission requirements, or error behaviors. It is consistent with annotations and adds minimal context beyond them.

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, front-loaded sentence with no redundant wording. Every word contributes to identifying the operation and its target resource, making it highly concise and scannable.

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?

For a simple one-parameter read-only lookup, the description is functionally sufficient to guide selection and invocation. A minor gap is that 'detailed information' is vague and there is no output schema, so the agent cannot anticipate the returned fields or structure.

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 covers the keyTag parameter fully with a clear description ('unique identifier derived from key name'). The tool description merely restates 'by its keyTag' without adding further format, provenance, or usage nuance, so it adds no value beyond 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?

Description uses a specific verb ('Get detailed information') plus resource ('KMS key') and identifier ('keyTag'), making the tool's purpose unambiguous. It clearly distinguishes from sibling tools like ncloud_kms_get_key_list or ncloud_kms_get_key_version_list, which serve different retrieval scopes.

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

Usage Guidelines3/5

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

The description implies the tool is for retrieving details of a single key when keyTag is known, but it does not explicitly state when to use this instead of alternatives such as ncloud_kms_get_key_list or ncloud_kms_get_key_version_list. No exclusions or alternative naming are provided.

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

Deploy Server