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

ncloud-gov-mcp-server

by sjk4425
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

ncloud_terminate_server

DestructiveIdempotent

Permanently terminate one or more server instances. Set confirm=true to execute the deletion.

Instructions

⚠️ Destructive: Permanently terminate (delete) one or more server instances. Set confirm=true to execute.

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_terminate_server"
  }
}

Input Schema

NameRequiredDescriptionDefault
confirmNoMust be true to actually execute the destructive operation
serverInstanceNoListYesList of server instance numbers to terminate

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

A4.2/5.0
Behavior4/5

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

The description adds the critical requirement 'Set confirm=true to execute' and emphasizes 'Permanently', giving the agent essential behavioral context beyond the destructiveHint annotation. It does not contradict annotations and provides useful guardrail information for a destructive operation.

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 well-structured sentence that front-loads the destructive warning and immediately states the execution requirement. Every word adds value, and there is no redundant or filler content.

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 two-parameter destructive tool with annotations covering idempotency and destructiveness, the description provides sufficient context including the confirm flag. It does not explain what happens to associated resources or error behavior, but that is beyond the minimal necessary for correct invocation.

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%, and the description does not add significant parameter-level detail beyond what the schema already provides (e.g., serverInstanceNoList and confirm). The phrase 'one or more server instances' aligns with the array type but adds no new semantic meaning.

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 a specific verb ('terminate') and resource ('server instances'), and explicitly says 'permanently terminate (delete)' to distinguish it from stop/reboot operations. This provides precise purpose clarity that differentiates it from sibling tools like ncloud_stop_server or ncloud_reboot_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 description clearly implies this is for permanent deletion via the word 'terminate (delete)' and the destructive warning. It does not explicitly name alternatives like stop or reboot, but the context is clear enough for an agent to infer when to use this tool versus temporary operations.

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