ncloud-gov-mcp-server

ncloud_ses_set_snapshot_schedule

Idempotent

Configure cron-based snapshot backups for Search Engine Service clusters, using cluster instance number, bucket name, and schedule expression.

Instructions

Set snapshot scheduling for a Search Engine Service cluster

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>",
      "bucketName": "<bucketName>",
      "scheduleExpression": "<scheduleExpression>"
    },
    "name": "ncloud_ses_set_snapshot_schedule"
  }
}

Input Schema

Name	Required	Description
`bucketName`	Yes	Object Storage bucket name
`scheduleExpression`	Yes	Cron expression for scheduling
`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 declare idempotentHint=true and destructiveHint=false, so the safety profile is clear. The description adds no extra behavioral context (e.g., whether an existing schedule is overwritten, any required cluster state). It does not contradict 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?

The description is a single, concise sentence that is front-loaded with the main action and object. No unnecessary words or repetition.

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?

For a simple 3-parameter tool with full schema descriptions, the description is adequate but lacks context about usage, prerequisites, or the expected effect of setting a schedule. It is not fully complete for a configuration-setting operation.

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%, with each parameter already described in the input schema. The description itself adds no parameter-specific details, but given the high schema coverage, the parameters are sufficiently documented.

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') and the resource ('snapshot scheduling' for a Search Engine Service cluster). It is specific and distinguishes from related tools like ncloud_ses_unset_snapshot_schedule 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 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 versus alternatives such as ncloud_ses_unset_snapshot_schedule or ncloud_ses_get_snapshot_history. It does not mention prerequisites or situations where this tool should or shouldn't be used.

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

Deploy Server