ncloud-gov-mcp-server

ncloud_ses_set_snapshot_api_key

Idempotent

Set API authentication keys for Object Storage access to enable snapshot operations on a specified cluster instance.

Instructions

Set API authentication key for Object Storage access (for snapshots)

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": {
      "serviceGroupInstanceNo": "<serviceGroupInstanceNo>",
      "accessKeyId": "<accessKeyId>",
      "secretAccessKey": "<secretAccessKey>"
    },
    "name": "ncloud_ses_set_snapshot_api_key"
  }
}

Input Schema

Name	Required	Description
`accessKeyId`	Yes	Object Storage access key
`secretAccessKey`	Yes	Object Storage secret key
`serviceGroupInstanceNo`	Yes	Cluster instance number

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.1Aug 2, 2026

TDQS

A3.5/5.0

Behavior3/5

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

Annotations already indicate idempotentHint=true and destructiveHint=false, so the safety profile is known. The description adds context that this key is for Object Storage access specifically for snapshots, but does not disclose whether the key replacement is immediate, whether existing snapshots are affected, or any other operational side effects.

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?

A single, well-structured sentence with no filler. It is front-loaded with the action and resource, and the parenthetical clarifies the frame without redundancy.

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 full schema coverage and the presence of annotations, the description is minimally viable. However, it does not explain the relationship to other snapshot operations (e.g., that this key may be required before creating or exporting snapshots), nor does it mention any prerequisites or side effects. For a simple configuration tool this is acceptable but not comprehensive.

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 baseline is 3. The description adds minimal context beyond what the schema provides: it clarifies that the access keys are for Object Storage access in the context of snapshots, but does not elaborate on how the keys are used or the role of the cluster instance number.

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 action ('Set'), the resource ('API authentication key'), and the context ('for Object Storage access (for snapshots)'). This distinguishes it from sibling tools that manage snapshots or schedules, such as ncloud_ses_set_snapshot_schedule.

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

Usage Guidelines2/5

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

The description provides no guidance on when to use this tool, prerequisites, or alternatives. It does not mention whether this should be called before snapshot creation or how it relates to other snapshot-related operations.

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

Deploy Server