Skip to main content
Glama
sjk4425

ncloud-mcp-server

by sjk4425

ncloud_kms_create_key

Create a new KMS key in Naver Cloud, supporting AES256 symmetric, RSA2048 asymmetric, or ECDSA key types. Configure storage type, auto-rotation, and convergent encryption.

Instructions

Create a new KMS key. Supports AES256 (symmetric), RSA2048 (asymmetric), and ECDSA key types.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
memoNoKey memo/description (0-100 chars)
keyNameYesKey name (3-15 chars, alphanumeric + '-' + '_', must start with letter)
keyTypeYesKey type: AES256 (symmetric 256-bit), RSA2048 (asymmetric 2048-bit), ECDSA (asymmetric 256-bit)
isConvergentNoEnable convergent encryption (only for AES256, default: false)
isAutoRotationNoEnable auto rotation (default: false)
protectionTypeYesKey storage type: BASIC (encrypted internal storage) or COMMON_HSM (Hardware Security Module)
rotationPeriodNoAuto rotation period in days (1-730, default: 90). Only when isAutoRotation is true
Behavior3/5

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

Annotations provide destructiveHint: false. The description adds no extra behavioral context such as async behavior, costs, or validation steps beyond stating it creates a key.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is two sentences and front-loaded with the action. It is concise but could include more contextual information without becoming verbose.

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 7 parameters and no output schema, the description does not explain return values, prerequisites, or success/failure outcomes. It is adequate but lacks completeness for a creation operation.

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 description coverage is 100%, so all parameters are already described. The description adds no additional meaning 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 clearly states the tool creates a new KMS key and lists the supported key types. It distinguishes this creation tool from sibling tools like get, enable, disable, etc.

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 usage when a new key is needed, but does not provide explicit when-to-use or when-not-to-use guidance. It does not differentiate between 'create_key' and 'create_custom_key' among siblings.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/sjk4425/ncloud-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server