Skip to main content
Glama
sjk4425

ncloud-mcp-server

by sjk4425
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

ncloud_nks_update_lb_subnet

Idempotent

Update the load balancer subnet for an NKS cluster by specifying a subnet number and public/private type, or up to two subnet numbers for multi-zone public setups.

Instructions

Update the load balancer subnet of an NKS cluster. Parameters are sent as query string (no JSON body): lbSubnetNo (or, Public zone only, lbSubnetNoList with up to 2 subnets in different zones) plus igwYn (Y = public subnet, N = private, default).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
igwYnNoSubnet type: Y = public LB subnet, N = private (default)
lbSubnetNoNoLoad balancer subnet instance number (required unless lbSubnetNoList is given)
clusterUuidYesUUID of the cluster
lbSubnetNoListNoPublic zone only: up to 2 LB subnet instance numbers in different zones (multi-zone). Alternative to lbSubnetNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changedv2.0.1
    • addedInput schema / properties / igwYn
      Added value: +{
+  "description": "Subnet type: Y = public LB subnet, N = private (default)",
+  "enum": [
+    "Y",
+    "N"
+  ],
+  "type": "string"
+}
    • removedInput schema / properties / lbPrivateSubnetNo
      Removed value: -{
-  "description": "New LB private subnet number",
-  "type": "number"
-}
    • removedInput schema / properties / lbPublicSubnetNo
      Removed value: -{
-  "description": "New LB public subnet number",
-  "type": "number"
-}
    • addedInput schema / properties / lbSubnetNo
      Added value: +{
+  "description": "Load balancer subnet instance number (required unless lbSubnetNoList is given)",
+  "type": "number"
+}
    • addedInput schema / properties / lbSubnetNoList
      Added value: +{
+  "description": "Public zone only: up to 2 LB subnet instance numbers in different zones (multi-zone). Alternative to lbSubnetNo",
+  "items": {
+    "type": "number"
+  },
+  "maxItems": 2,
+  "type": "array"
+}
  2. First observedv1.10.1

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare idempotentHint=true and destructiveHint=false, so safety of repeated calls is covered. The description adds one genuinely useful behavioral detail -- parameters are transmitted as a query string with no JSON body -- but says nothing about side effects on live traffic, prerequisites, or whether the change is disruptive. With annotations covering the safety profile, a 3 is warranted.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two front-loaded sentences with no filler; the mutation and its scoping constraints come first. The nested parenthetical in the second sentence is dense but every clause carries information, so it stays within budget.

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?

No output schema exists, but for an update tool with full schema coverage and annotations covering idempotency/destructiveness, the description supplies the needed invocation context (transport format, alternative parameters, enum meaning). Return values and any post-update state effects are the only omissions, which is acceptable here.

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%, so the baseline is 3. The description restates the cross-parameter constraints (lbSubnetNo vs lbSubnetNoList, Public-zone-only, up to 2 subnets) that the schema already documents, adding only the query-string transport note, which is marginal rather than compensating for any gap.

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?

States a specific verb and resource: 'Update the load balancer subnet of an NKS cluster.' The NKS/LB scope lets an agent distinguish it from the classic-LB sibling ncloud_set_lb_subnet and from ncloud_nks_update_node_pool_subnet without opening a schema.

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

Usage Guidelines3/5

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

Gives a conditional usage rule at the parameter level (lbSubnetNoList is 'Public zone only' for multi-zone) and notes igwYn's default, which implies context. However, it never states when this tool should be chosen over related siblings such as ncloud_nks_update_node_pool_subnet or ncloud_set_lb_subnet, so tool-level routing guidance is absent.

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