Skip to main content
Glama
sjk4425

ncloud-mcp-server

by sjk4425
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

ncloud_get_cache_target_subnets

Read-only

List subnets in a VPC that can be used to create a Cloud DB for Cache instance, with options to filter by public/private and region.

Instructions

List subnets available for creating a Cloud DB for Cache instance in a VPC

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
vpcNoYesVPC number (from ncloud_get_cache_target_vpcs)
isPublicNotrue: public subnets only, false: private subnets only
regionCodeNoRegion code (e.g., KR, JPN, SGN)
cloudCacheImageProductCodeYesCache image product code (from ncloud_get_cache_image_products)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changedv1.15.0
    • addedInput schema / properties / cloudCacheImageProductCode
      Added value: +{
+  "description": "Cache image product code (from ncloud_get_cache_image_products)",
+  "type": "string"
+}
    • removedInput schema / properties / cloudCacheInstanceNo
      Removed value: -{
-  "description": "Cloud Cache instance number",
-  "type": "string"
-}
    • addedInput schema / properties / isPublic
      Added value: +{
+  "description": "true: public subnets only, false: private subnets only",
+  "type": "boolean"
+}
    • addedInput schema / properties / vpcNo
      Added value: +{
+  "description": "VPC number (from ncloud_get_cache_target_vpcs)",
+  "type": "string"
+}
    • changedInput schema / required
      Previous value: -[
-  "cloudCacheInstanceNo"
-]New value: +[
+  "vpcNo",
+  "cloudCacheImageProductCode"
+]
  2. First observedv1.10.1

TDQS

A4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, so the agent knows this is a safe read operation. The description adds the context that these subnets are tied to a specific VPC and creation use case, but it does not disclose output shape, pagination, or filtering behavior beyond what the schema already provides.

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 with no filler or redundant restatement of the tool name. It communicates the verb, resource, and scope efficiently.

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 schema coverage, the description plus schema are sufficient for an agent to call it correctly. The lack of an output schema is not a major gap here because the resource being listed is clear from the description.

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%, so the schema already documents all four parameters, including their source tools and isPublic semantics. The description adds no extra parameter meaning beyond that, which matches the baseline for high schema coverage.

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 ('List') and resource ('subnets available for creating a Cloud DB for Cache instance in a VPC'), which clearly identifies this as the subnet lookup step for cache instances. It is easily distinguished from siblings like ncloud_get_cache_target_vpcs (VPCs) and the many other get_*_target_subnets tools for MySQL, MSSQL, MongoDB, etc.

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 provides clear context for use: it is the tool to call when selecting a subnet for creating a Cloud DB for Cache instance. It does not explicitly name alternatives or exclusions, but the intended placement in the cache creation workflow is clear, and the schema parameter descriptions reference the prerequisite source tools.

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