ncloud-gov-mcp-server

ncloud_create_target_group

Create a load balancer target group by specifying VPC, protocol, target type, and health check parameters to manage backend instances.

Instructions

Create a new target group for a load balancer

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": {
      "vpcNo": "<vpcNo>",
      "targetGroupProtocolTypeCode": "<targetGroupProtocolTypeCode>",
      "targetTypeCode": "<targetTypeCode>"
    },
    "name": "ncloud_create_target_group"
  }
}

Input Schema

Name	Required	Description
`vpcNo`	Yes	VPC number
`targetNoList`	No	List of target numbers to bind to the target group at creation
`targetTypeCode`	Yes	Target type code (VSVR)
`healthCheckPort`	No	Health check port
`targetGroupName`	No	Target group name (max 30 characters)
`targetGroupPort`	No	Target group port number
`healthCheckCycle`	No	Health check cycle in seconds (5-300, default: 30)
`algorithmTypeCode`	No	Load balancing algorithm (RR, LC, SIPHS, MH)
`healthCheckUrlPath`	No	Health check URL path (for HTTP/HTTPS)
`healthCheckUpThreshold`	No	Healthy threshold count (2-10, default: 2)
`targetGroupDescription`	No	Target group description
`healthCheckDownThreshold`	No	Unhealthy threshold count (2-10, default: 2)
`healthCheckProtocolTypeCode`	No	Health check protocol (HTTP, HTTPS, TCP)
`targetGroupProtocolTypeCode`	Yes	Target group protocol type (HTTP, HTTPS, TCP, PROXY_TCP)
`healthCheckHttpMethodTypeCode`	No	HTTP method type for health check (HEAD, GET). Required if healthCheckProtocolTypeCode is HTTP or HTTPS

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.1Aug 2, 2026

TDQS

B3.2/5.0

Behavior2/5

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

With only destructiveHint=false in annotations, the description carries the burden of behavioral disclosure. It does not mention that the target group may need to be attached to a load balancer later, what the response contains (e.g., targetGroupNo), or any side effects. The description is minimal and does not add meaningful 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 sentence, front-loaded with the verb, and contains no fluff. It earns its place by adding the load balancer context, making it appropriately sized and structured.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a complex tool with 15 parameters and no output schema, the description is incomplete. It does not explain the target group's role in load balancing, when it should be created relative to load balancers, or what the expected response is. The agent would need to rely on schema and sibling names, which is insufficient for confident 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%, so the baseline is 3. The description itself adds no parameter-level information, but all parameters already have descriptions in the schema. This is acceptable but not enhanced.

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 action ('Create') and resource ('a new target group for a load balancer'), which distinguishes it from sibling tools like list/get/change/delete target groups. It adds the load balancer context, making the purpose unambiguous.

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

Usage Guidelines2/5

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

The description gives no guidance on when to use this tool versus alternatives, such as creating a load balancer first or modifying an existing target group. It lacks prerequisites (e.g., existing VPC) and does not mention related tools like change_target_group_config or list_target_groups.

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

Deploy Server