ncloud-gov-mcp-server

ncloud_stop_server

Idempotent

Stop one or more running server instances by specifying their instance numbers. Reduce costs and manage resources by powering down unused servers.

Instructions

Stop one or more running server instances

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": {
      "serverInstanceNoList": "<serverInstanceNoList>"
    },
    "name": "ncloud_stop_server"
  }
}

Input Schema

Name	Required	Description	Default
`serverInstanceNoList`	Yes	List of server instance numbers to stop

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.1Aug 2, 2026

TDQS

B3.3/5.0

Behavior3/5

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

Annotations declare idempotentHint=true and destructiveHint=false, and the description does not contradict them. The description adds that target instances are 'running' but does not explain the post-stop state, restartability, or side effects. With annotations covering safety, this is acceptable but not deeply informative.

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, front-loaded sentence that efficiently conveys the action and scope. There is no repetition, filler, or unnecessary detail.

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?

With one required parameter, idempotent and non-destructive annotations, and a clear sentence, the description is minimally sufficient. However, it lacks information about expected results (e.g., operation status or how to verify) and how to obtain server instance numbers, which would aid an agent in a full workflow.

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 fully describes the sole parameter serverInstanceNoList as a list of server instance numbers to stop. The description adds no additional format, constraints, or semantic detail beyond the schema, so the baseline for high schema coverage applies.

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 uses a specific verb (Stop) and resource (running server instances) and clearly indicates support for multiple instances. It does not explicitly distinguish from sibling lifecycle operations like ncloud_interrupt_server or ncloud_terminate_server, but the core purpose is unambiguous.

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?

No guidance is provided on when to use this tool versus alternatives such as ncloud_start_server, ncloud_reboot_server, ncloud_interrupt_server, or ncloud_terminate_server. The description only states the action without any usage context or exclusions.

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

Deploy Server