Skip to main content
Glama
sjk4425

ncloud-mcp-server

by sjk4425
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

ncloud_ses_set_snapshot_api_key

Idempotent

Set Object Storage API credentials for snapshots to enable snapshot management and avoid error 10115.

Instructions

Set the Object Storage API authentication key used for snapshots. This is the first step of the snapshot chain — ncloud_ses_get_snapshot_buckets, ncloud_ses_create_snapshot and the scheduling tools all fail with 10115 until it is set.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
secretKeyYesObject Storage secret key
accessKeyIdYesObject Storage access key
serviceGroupInstanceNoYesCluster instance number

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv1.15.0
    • removedInput schema / properties / secretAccessKey
      Removed value: -{
-  "description": "Object Storage secret key",
-  "type": "string"
-}
    • addedInput schema / properties / secretKey
      Added value: +{
+  "description": "Object Storage secret key",
+  "type": "string"
+}
    • changedInput schema / required
      Previous value: -[
-  "serviceGroupInstanceNo",
-  "accessKeyId",
-  "secretAccessKey"
-]New value: +[
+  "serviceGroupInstanceNo",
+  "accessKeyId",
+  "secretKey"
+]
  2. First observedv1.10.1

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already mark the tool as idempotent and non-destructive. The description adds behavioral context beyond that: the prerequisite relationship and the specific 10115 failure downstream. This helps an agent understand the operational consequence of skipping this tool.

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?

Two sentences with no filler. The core action is front-loaded, and the second sentence provides critical sequencing information that directly informs calling behavior.

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 3-parameter set-key operation with no output schema, the description is complete enough: it states what the tool does, what credentials are involved, and why it must be called first. It does not explain return values, but that is not essential for selecting and invoking this tool.

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 the schema fully documents serviceGroupInstanceNo, accessKeyId, and secretKey. The description adds general context about Object Storage authentication but does not add parameter-specific meaning beyond what the schema already provides, matching the baseline of 3.

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 states a specific verb ('Set') and resource ('Object Storage API authentication key used for snapshots'), and it names the downstream chain it belongs to. This clearly distinguishes it from sibling snapshot tools like ncloud_ses_get_snapshot_buckets and ncloud_ses_create_snapshot.

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 provides clear usage context by identifying this as the first step of the snapshot chain and explicitly warning that sibling tools fail with 10115 until it is set. It does not enumerate when-not-to-use cases, but the sequencing guidance is strong enough for an agent to decide when to invoke it.

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