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

ncloud-mcp-server

by sjk4425
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

ncloud_cdss_get_subnet_list

Read-only

Lists available subnets for CDSS cluster creation by taking an OS product code and VPC number, helping you choose a valid subnet for G2 clusters.

Instructions

Get available subnet list for CDSS cluster creation (G2)

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": {
      "softwareProductCode": "<softwareProductCode>",
      "vpcNo": "<vpcNo>"
    },
    "name": "ncloud_cdss_get_subnet_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
vpcNoYesVPC number (from ncloud_cdss_get_vpc_list)
softwareProductCodeYesOS type code (from ncloud_cdss_get_os_products)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv1.15.0
    • addedInput schema / properties / softwareProductCode
      Added value: +{
+  "description": "OS type code (from ncloud_cdss_get_os_products)",
+  "type": "string"
+}
    • changedInput schema / properties / vpcNo / description
      Previous value: -"VPC number to filter subnets"New value: +"VPC number (from ncloud_cdss_get_vpc_list)"
    • addedInput schema / required
      Added value: +[
+  "softwareProductCode",
+  "vpcNo"
+]
  2. First observedv1.10.1

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, and the description's 'Get' is consistent. The description adds the G2 and cluster-creation scoping, but does not disclose response format, pagination, or any requirements beyond what the schema/annotations offer. This meets the minimum bar but adds little extra 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?

A single front-loaded sentence communicates purpose, scope, and generation with zero wasted words. It is appropriately sized for a simple read-only list tool.

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?

For a read-only list tool with fully documented parameters and readOnly annotation, the description is largely sufficient – 'Get available subnet list' conveys the return. It does not explicitly mention the G3 sibling or when to prefer the other generation, so a small gap remains, but nothing essential is missing.

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%, and the parameter descriptions already state that vpcNo comes from ncloud_cdss_get_vpc_list and softwareProductCode from ncloud_cdss_get_os_products. The tool description does not add parameter-level meaning, so it holds at baseline 3.

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 states the tool returns the available subnet list for CDSS cluster creation and scopes it to G2, distinguishing it from the sibling ncloud_cdss_get_subnet_list_g3. This is a specific verb + resource with an explicit generation qualifier, so an agent can select it without inspecting the 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?

The phrase 'for CDSS cluster creation (G2)' implies when to use it, but the description does not explicitly name ncloud_cdss_get_subnet_list_g3 as the alternative for G3 clusters or provide any when-not guidance. Context is clear but exclusions/alternatives are left to inference.

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