ncloud-gov-mcp-server

ncloud_sourcedeploy_get_target_groups

Read-only

Get the list of load balancer target groups associated with an Auto Scaling group to manage traffic distribution and deployment targets.

Instructions

Get the list of load balancer target groups connected to an Auto Scaling group

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": {
      "autoScalingGroupNo": "<autoScalingGroupNo>"
    },
    "name": "ncloud_sourcedeploy_get_target_groups"
  }
}

Input Schema

Name	Required	Description	Default
`autoScalingGroupNo`	Yes	Auto Scaling group number

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.1Aug 2, 2026

TDQS

A4/5.0

Behavior3/5

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

Annotations declare readOnlyHint=true, and the description's 'Get' verb aligns with a read-only operation. The description adds the scoping to an ASG, which is useful context, but doesn't disclose additional behavioral details like pagination or return format. Since annotations cover the safety profile, a score of 3 is appropriate.

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?

A single sentence conveys the purpose without extraneous words. It is front-loaded and efficient.

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's simplicity (one parameter, read-only annotation, no output schema), the description adequately states the operation's scope. However, it doesn't cover expected return value structure or edge cases, which would be helpful but not critical.

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?

The input schema fully documents the single parameter with a clear description: 'Auto Scaling group number'. The description reinforces its role by mentioning 'connected to an Auto Scaling group', but doesn't add novel semantic detail beyond 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 a specific verb 'Get' and identifies the exact resource: 'load balancer target groups connected to an Auto Scaling group'. This clearly distinguishes it from sibling getters like ncloud_sourcedeploy_get_autoscaling_groups or ncloud_sourcedeploy_get_servers.

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 implies the use case: when you need target groups associated with a specific ASG. It provides clear context but does not explicitly name alternatives or exclusions, so it falls short of full when/when-not guidance.

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

Deploy Server