ncloud-gov-mcp-server

ncloud_kms_create_token_set

Generate an access token and refresh token pair for NCP Gov Cloud authentication, using an active token generator.

Instructions

Create a token set (access token + refresh token) for token-based authentication. Requires an active token generator.

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

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

A4/5.0

Behavior3/5

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

Annotations only declare destructiveHint=false, so the description adds the clue that this is a creation operation requiring an active token generator. However, it does not disclose what happens if the generator is missing, whether existing token sets are affected, or any rate/expiration details. It adds minimal behavioral context beyond 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?

One sentence, front-loaded with the action, includes a parenthetical clarification and an important prerequisite. Zero wasted words.

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 single-parameter creation tool with no output schema, the description provides the essential purpose and a prerequisite. The response isn't described, but the phrase 'access token + refresh token' hints at the expected output. It is nearly complete, though it could be stronger by stating the exact result or ties to the token generator key tag.

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 schema already describes keyTag at 100% coverage, so the baseline is 3. The description adds no further semantic detail about the parameter, though it does relate the token generator prerequisite to the overall workflow.

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 uses a specific verb+resource ('Create a token set') and explains the composition (access token + refresh token) and purpose (token-based authentication). It also includes a prerequisite that distinguishes it from the sibling ncloud_kms_create_token_generator, which creates a different entity.

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?

It clearly states the purpose and the requirement of an active token generator, giving the agent a condition to check before invoking. It does not explicitly name alternatives or exclusions, but the context is clear enough for this tool's niche.

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

Deploy Server