Skip to main content
Glama
sjk4425

ncloud-mcp-server

by sjk4425
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

ncloud_ses_get_subnet_list_g3

Read-only

Get available subnets for creating a Search Engine Service G3 cluster by specifying the VPC and OS image, with optional filtering by private or public subnets.

Instructions

Get available subnet list for Search Engine Service cluster creation (G3/KVM only)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
vpcNoYesVPC number (from ncloud_ses_get_vpc_list)
isPrivateNotrue: private subnets only, false: public subnets only
softwareProductCodeYesG3 OS image code (from ncloud_ses_get_cluster_server_images)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv1.15.0
    • addedInput schema / properties / isPrivate
      Added value: +{
+  "description": "true: private subnets only, false: public subnets only",
+  "type": "boolean"
+}
    • addedInput schema / properties / softwareProductCode
      Added value: +{
+  "description": "G3 OS image code (from ncloud_ses_get_cluster_server_images)",
+  "type": "string"
+}
    • changedInput schema / properties / vpcNo / description
      Previous value: -"VPC number"New value: +"VPC number (from ncloud_ses_get_vpc_list)"
    • changedInput schema / required
      Previous value: -[
-  "vpcNo"
-]New value: +[
+  "softwareProductCode",
+  "vpcNo"
+]
  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?

With readOnlyHint=true already covering the safe read-only nature, the description adds the G3/KVM-only scope and its purpose in cluster creation. It does not go further to describe the return format, filtering behavior, or whether the list is scoped to a specific VPC beyond what the schema implies. This is acceptable but not rich.

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 conveys the operation, resource, and key constraint without wasted words. Every element earns its place and the length is proportional to the simple tool it documents.

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?

For a read-only list tool with 100% schema coverage and a readOnlyHint annotation, the description is mostly sufficient to guide invocation. However, there is no output schema and the description does not hint at what the returned subnet list contains or any pagination/ordering behavior, leaving a small but noticeable gap for an agent expecting a complete picture.

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 input schema already documents all three parameters with meaningful descriptions (e.g., source functions for vpcNo and softwareProductCode). The description adds no parameter-level detail, but the schema carries the full burden, so the baseline score of 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 states a specific verb ('Get'), a concrete resource ('available subnet list'), and a clear scope ('for Search Engine Service cluster creation (G3/KVM only)'). The 'G3/KVM only' qualifier distinguishes it from the sibling ncloud_ses_get_subnet_list and other similar list tools.

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 description implies when to use the tool: when preparing SES cluster creation on G3/KVM infrastructure. However, it does not explicitly name alternatives or say when NOT to use it, such as pointing to ncloud_ses_get_subnet_list for non-G3 environments. The usage context is clear but the exclusion/alternative guidance is 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