ncloud-gov-mcp-server

ncloud_reboot_cache_server

Idempotent

Provide a Cloud Cache server instance number to reboot it, restoring service or applying updates.

Instructions

Reboot a Cloud DB for Cache server instance

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": {
      "cloudCacheServerInstanceNo": "<cloudCacheServerInstanceNo>"
    },
    "name": "ncloud_reboot_cache_server"
  }
}

Input Schema

Name	Required	Description	Default
`cloudCacheServerInstanceNo`	Yes	Cloud Cache server instance number to reboot

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.1Aug 2, 2026

TDQS

A4/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, establishing the safety profile. The description adds no extra behavioral context such as potential downtime, duration, or post-reboot status. It simply restates the action without additional transparency beyond 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?

A single sentence with no filler or redundancy. The description is front-loaded with the action and resource, making it immediately scannable and efficient.

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?

Given the low complexity (one required parameter), the presence of idempotent and non-destructive annotations, and the absence of an output schema, the description is sufficient to understand the tool's function. It could mention that the reboot may temporarily disrupt the cache service, but that is not essential given the clear action.

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 input schema has 100% coverage for the single parameter, including a clear description ('Cloud Cache server instance number to reboot'). The tool description adds no additional meaning, examples, or format details beyond the schema, so the baseline of 3 is appropriate.

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 uses a specific action ('Reboot') and a specific resource ('Cloud DB for Cache server instance'), which clearly distinguishes it from sibling reboot tools like ncloud_reboot_mysql_server or ncloud_reboot_server. It is concise and unambiguous.

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 clearly identifies the resource type, making it evident when this tool should be used (for Cloud DB for Cache instances) versus other reboot tools. However, it does not explicitly state exclusions or alternatives, falling slightly short of the full guidance provided in top-tier examples.

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

Deploy Server