Skip to main content
Glama
sjk4425

ncloud-mcp-server

by sjk4425
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

ncloud_ses_create_snapshot

Create a snapshot of a Search Engine Service cluster and store it in an Object Storage bucket for backup or recovery.

Instructions

Create a snapshot of a Search Engine Service cluster. ⚠️ Prerequisite chain: ncloud_ses_set_snapshot_api_key → ncloud_ses_get_snapshot_buckets → this tool. Without the API key the bucket lookup fails with 10115.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
bucketNameYesObject Storage bucket to store the snapshot in (from ncloud_ses_get_snapshot_buckets)
snapshotNameYesName for the snapshot
serviceGroupInstanceNoYesCluster instance number

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv1.15.0
    • changedInput schema / properties / bucketName / description
      Previous value: -"Object Storage bucket name for snapshot storage"New value: +"Object Storage bucket to store the snapshot in (from ncloud_ses_get_snapshot_buckets)"
    • addedInput schema / properties / snapshotName
      Added value: +{
+  "description": "Name for the snapshot",
+  "type": "string"
+}
    • changedInput schema / required
      Previous value: -[
-  "serviceGroupInstanceNo",
-  "bucketName"
-]New value: +[
+  "serviceGroupInstanceNo",
+  "snapshotName",
+  "bucketName"
+]
  2. First observedv1.10.1

TDQS

A3.8/5.0
Behavior3/5

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

Annotations only provide destructiveHint: false, so the description carries the burden of behavioral disclosure. It does disclose the prerequisite failure condition, but doesn't mention other behaviors like whether the operation is asynchronous, what it returns on success, or any side effects beyond creating a snapshot. This is some value but not comprehensive.

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 two concise sentences, front-loaded with the purpose and then the prerequisite warning. Every sentence earns its place with no fluff. The warning is clearly highlighted with ⚠️.

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?

All three parameters are documented, and the prerequisite chain helps the agent know how to prepare. However, the description doesn't explain what happens after creation (e.g., return value, polling for status). Given the low complexity of the operation and no output schema, this is mostly complete but could be slightly richer.

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 covers 100% of parameters with descriptions, including that bucketName comes from ncloud_ses_get_snapshot_buckets. The description doesn't add extra semantics beyond what the schema already provides, so baseline 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb ('Create') and resource ('snapshot of a Search Engine Service cluster'), making the purpose clear. It also mentions the prerequisite chain which adds context. However, it doesn't explicitly distinguish from other snapshot-related tools, though the resource type is unique enough to avoid confusion.

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?

The description provides a clear prerequisite chain (ncloud_ses_set_snapshot_api_key → ncloud_ses_get_snapshot_buckets → this tool) and warns about the failure if not followed (error 10115). This gives explicit sequential guidance, but doesn't discuss alternative tools or when not to use this tool.

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