Skip to main content
Glama
sjk4425

ncloud-mcp-server

by sjk4425
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

ncloud_ses_set_snapshot_schedule

Idempotent

Schedule daily snapshots for a Search Engine Service cluster by specifying bucket, snapshot name, and time. Requires a snapshot API key to be set beforehand.

Instructions

Set a daily snapshot schedule for a Search Engine Service cluster. ⚠️ Requires ncloud_ses_set_snapshot_api_key first (otherwise 10115).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
bucketNameYesObject Storage bucket to store snapshots in
scheduledDayYesScheduled day
snapshotNameYesName prefix for scheduled snapshots
scheduledHourYesScheduled hour
scheduledMinuteYesScheduled minute
serviceGroupInstanceNoYesCluster instance number

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed7 schema fields changedv1.15.0
    • changedInput schema / properties / bucketName / description
      Previous value: -"Object Storage bucket name"New value: +"Object Storage bucket to store snapshots in"
    • removedInput schema / properties / scheduleExpression
      Removed value: -{
-  "description": "Cron expression for scheduling",
-  "type": "string"
-}
    • addedInput schema / properties / scheduledDay
      Added value: +{
+  "description": "Scheduled day",
+  "type": "string"
+}
    • addedInput schema / properties / scheduledHour
      Added value: +{
+  "description": "Scheduled hour",
+  "type": "string"
+}
    • addedInput schema / properties / scheduledMinute
      Added value: +{
+  "description": "Scheduled minute",
+  "type": "string"
+}
    • addedInput schema / properties / snapshotName
      Added value: +{
+  "description": "Name prefix for scheduled snapshots",
+  "type": "string"
+}
    • changedInput schema / required
      Previous value: -[
-  "serviceGroupInstanceNo",
-  "bucketName",
-  "scheduleExpression"
-]New value: +[
+  "serviceGroupInstanceNo",
+  "snapshotName",
+  "bucketName",
+  "scheduledDay",
+  "scheduledHour",
+  "scheduledMinute"
+]
  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 provide idempotentHint=true and destructiveHint=false, so the safety profile is known. The description adds the critical dependency on the API key and the resulting error code (10115), which is behavioral context not present in the schema or annotations. It does not contradict 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?

The description is a single sentence with a critical warning appended. It is front-loaded with the action and resource, and the prerequisite warning is concise. No extraneous 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 configuration setter with no output schema, the description covers the essential action and the key prerequisite. Combined with the annotations (idempotent, non-destructive) and 100% parameter coverage, nothing critical is missing. It could have mentioned that the schedule recurs daily, but that's already in the purpose.

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 each parameter is documented (e.g., bucketName, scheduledHour). The description does not add meaning beyond the schema, but since coverage is high, a baseline of 3 is appropriate. It could have explained the format of scheduledDay/hour/minute, but the schema already labels them.

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 a daily snapshot schedule') and the resource ('Search Engine Service cluster'). It distinguishes from siblings like ncloud_ses_create_snapshot (one-off) and ncloud_ses_unset_snapshot_schedule (removing). The specificity of 'daily' further clarifies scope.

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 explicitly names a required prerequisite (ncloud_ses_set_snapshot_api_key) and the error code if not met, giving clear when-to-use guidance. It does not explicitly contrast with alternatives, but the prerequisite and the daily schedule nature make the usage context clear.

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