ncloud-gov-mcp-server

ncloud_remove_port_plugin

DestructiveIdempotent

Remove port monitoring plugins from a Ncloud server instance. Specify the instance number and ports, then set confirm=true to apply.

Instructions

⚠️ Destructive: Remove port monitoring plugin(s) from a server instance. 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": {
      "instanceNo": "<instanceNo>",
      "portList": "<portList>"
    },
    "name": "ncloud_remove_port_plugin"
  }
}

Input Schema

Name	Required	Description
`type`	No	Target type (default 'vpcserver')
`confirm`	No	Must be true to actually execute the destructive operation
`portList`	Yes	Port numbers to remove
`instanceNo`	Yes	Server instance number

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.1Aug 2, 2026

TDQS

A4/5.0

Behavior4/5

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

Annotations already include destructiveHint and idempotentHint. The description adds a warning and clarifies the confirm flag requirement, explaining that execution only happens when confirm=true. This goes beyond the annotations without contradicting them.

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?

One concise sentence with a warning prefix. Information is front-loaded and every word adds value; no redundancy or fluff.

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 destructive tool with 4 parameters and no output schema, the description covers the essential safety and execution requirements. It could mention prerequisites or side effects, but the current description is sufficient for an agent to select and invoke the tool correctly.

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%, so all parameters are documented in the schema. The description reinforces the confirm behavior already described in the schema but adds no new parameter-specific 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 'Remove port monitoring plugin(s) from a server instance' with a specific verb and resource. It distinguishes itself from sibling tools like ncloud_list_port_plugins, ncloud_add_port_plugin, and ncloud_set_port_plugins.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is implied (use when you want to remove port monitoring plugins), but there is no explicit when-to-use or when-not-to-use guidance or alternatives mentioned. The instruction 'Set confirm=true to execute' provides execution context but not tool-selection guidance.

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

Deploy Server