ncloud-mcp-server

ncloud_add_port_plugin

Add port monitoring plugins to a server instance by specifying the instance number and the ports to monitor. Ensures specific ports are monitored on Naver Cloud Platform infrastructure.

Instructions

Add port monitoring plugin(s) to a 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": {
      "instanceNo": "<instanceNo>",
      "portList": "<portList>"
    },
    "name": "ncloud_add_port_plugin"
  }
}

Input Schema

Name	Required	Description
`type`	No	Target type (default 'vpcserver')
`portList`	Yes	Port numbers to monitor
`instanceNo`	Yes	Server instance number

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.10.1Jul 29, 2026

TDQS

A3.9/5.0

Behavior3/5

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

The annotation destructiveHint=false already covers non-destructiveness. The description adds little beyond stating the add action; it does not disclose idempotency, whether existing plugins are preserved, or any server state requirements. No contradiction with annotations, but no extra behavioral context.

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, clear sentence with no filler words. It is appropriately front-loaded and concise.

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?

The tool has a simple 3-parameter schema and a non-destructive annotation, but no output schema. The description does not mention response format, error conditions, or how this differs from ncloud_set_port_plugins, leaving some gaps for an agent. However, the schema and annotation provide adequate baseline context for a basic add operation.

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%, with all three properties described (type with default and enum, portList as port numbers, instanceNo as server instance number). The tool description adds no parameter-level meaning beyond the schema, matching the baseline for high coverage.

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 ('Add') and resource ('port monitoring plugin(s)') and targets 'a server instance', clearly distinguishing it from sibling tools like ncloud_list_port_plugins or ncloud_remove_port_plugin. It immediately conveys the action and scope.

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 gives clear context that this tool is for adding port monitoring plugins to a server, which distinguishes it from list/remove/get/set siblings. However, it does not explicitly mention when not to use it or name alternatives, so it lacks full exclusion guidance.

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

Deploy Server