Skip to main content
Glama
Sign In
ncloud-gov-mcp-server

ncloud-gov-mcp-server

by sjk4425
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

ncloud_change_target_group_config

Idempotent

Update target group load balancing settings including algorithm, sticky sessions, and proxy protocol to optimize traffic distribution.

Instructions

Change target group configuration (algorithm, sticky session, proxy protocol)

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>"
    },
    "name": "ncloud_change_target_group_config"
  }
}

Input Schema

NameRequiredDescriptionDefault
targetGroupNoYesTarget group number
useProxyProtocolNoWhether to use proxy protocol (true/false). Available for PROXY_TCP protocol only
useStickySessionNoWhether to enable per-session access (true/false). Available for TCP, UDP, HTTP, HTTPS protocols
algorithmTypeCodeNoLoad balancing algorithm type code (RR, SIPHS, LC, MH). HTTP/HTTPS/PROXY_TCP: RR|SIPHS|LC, TCP/UDP: RR|MH

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

A3.5/5.0
Behavior3/5

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

Annotations declare the operation as idempotent and non-destructive, and the description does not contradict this. However, the description adds no extra behavioral context beyond listing the configurable parameters, which are already in the schema. It does not disclose immediate effects, protocol constraints, or potential impact on traffic.

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, front-loaded sentence that clearly states the action and resource, with a parenthetical list of settings. Every word earns its place; there is no redundancy.

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 description is adequate for a simple configuration change tool given the rich schema and safety annotations, but it is minimal. It does not mention return values, whether changes apply immediately, or any usage caveats. For a mutating operation without an output schema, slightly more context would be beneficial.

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 coverage is 100% with all four parameters well described. The description lists three configurable aspects, adding a high-level summary but no new detail beyond the schema. Baseline 3 is appropriate.

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 identifies the tool's purpose: changing target group configuration, specifically algorithm, sticky session, and proxy protocol. This is specific and distinguishes it from sibling tools like health check or description updates.

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?

No guidance is provided on when to use this tool versus alternatives. It does not mention prerequisites, related tools, or specify that it is for modifying these particular settings while other tools handle health checks or descriptions.

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

Deploy Server

Other Tools