ncloud-gov-mcp-server

ncloud_set_targets

Idempotent

Replace all targets in a target group with a specified list of server instance numbers, updating the instances that receive traffic.

Instructions

Set targets for a target group (replaces all existing targets with the specified list)

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": {
      "targetGroupNo": "<targetGroupNo>",
      "targetNoList": "<targetNoList>"
    },
    "name": "ncloud_set_targets"
  }
}

Input Schema

Name	Required	Description	Default
`targetNoList`	Yes	List of target (server instance) numbers to set (replaces existing targets)
`targetGroupNo`	Yes	Target group number

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.1Aug 2, 2026

TDQS

A4.2/5.0

Behavior4/5

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

The description explicitly discloses the key behavioral trait that all existing targets are replaced, which is not covered by the idempotentHint or destructiveHint annotations. This is critical for the agent to understand the full impact of the call.

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, concise sentence that clearly communicates the action and its replacement effect. Every word contributes value, with no redundancy or filler.

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?

Given the tool has only two required parameters and a complete schema, the description provides sufficient context for correct invocation. It does not describe return values, but for a set operation this is often implicit and the idempotentHint annotation adds further context.

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%: both targetGroupNo and targetNoList are already described in the input schema. The tool description adds no new parameter-level semantics beyond reinforcing the replacement behavior already stated in the schema.

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 the specific verb 'Set' and names the resource 'targets for a target group', then clarifies that it replaces all existing targets. This clearly distinguishes it from incremental tools like ncloud_add_target and ncloud_remove_target.

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 states that the operation replaces all existing targets, implying it should be used when a complete replacement is needed rather than incremental changes. It does not explicitly name alternative tools, but the replacement context provides clear guidance relative to sibling tools like ncloud_add_target and ncloud_remove_target.

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

Deploy Server