Skip to main content
Glama
Sign In
ncloud-gov-mcp-server

ncloud-gov-mcp-server

by sjk4425
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

ncloud_start_server

Idempotent

Start one or more stopped server instances by providing their server instance numbers.

Instructions

Start one or more stopped 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_start_server"
  }
}

Input Schema

NameRequiredDescriptionDefault
serverInstanceNoListYesList of server instance numbers to start

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

A4/5.0
Behavior3/5

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

Annotations already declare the tool is idempotent and non-destructive, so the safety profile is covered. The description adds a meaningful precondition (instances must be stopped) and indicates multiple instances are supported, but it does not describe response behavior or any additional side effects.

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 seven-word sentence with no filler or redundancy. Every word contributes to conveying the tool's action and target condition.

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 simple one-parameter start action with robust annotations and no output schema, the description combined with the schema provides sufficient information for an agent to select and invoke the tool. It could mention return values or status updates, but the low complexity makes the current level acceptable.

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 fully documents the sole parameter serverInstanceNoList with type, minItems, and description. The description's 'one or more' reiterates the schema's minItems constraint and adds no new semantic detail beyond what the schema already provides.

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 verb 'Start' plus the resource 'server instances' and qualifies the target as 'stopped', which clearly distinguishes it from sibling tools like ncloud_stop_server, ncloud_reboot_server, and ncloud_terminate_server.

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 phrase 'stopped server instances' provides a clear precondition for when to use this tool, implying it is only for instances currently in a stopped state. It does not explicitly name alternatives or exclusion cases, but the context is unambiguous enough for correct selection.

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