Skip to main content
Glama
sjk4425

ncloud-mcp-server

by sjk4425
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

ncloud_hadoop_list_target_subnets

Read-only

Find subnets available for Cloud Hadoop deployment by filtering with VPC and cluster image product code, with optional public/private filter.

Instructions

List subnets available for Cloud Hadoop deployment

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
vpcNoYesVPC number (from ncloud_hadoop_list_target_vpcs)
isPublicNotrue: public subnets only, false: private subnets only
regionCodeNoRegion code
cloudHadoopImageProductCodeYesCluster image product code (from ncloud_hadoop_list_image_products)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changedv1.15.0
    • addedInput schema / properties / cloudHadoopImageProductCode
      Added value: +{
+  "description": "Cluster image product code (from ncloud_hadoop_list_image_products)",
+  "type": "string"
+}
    • addedInput schema / properties / isPublic
      Added value: +{
+  "description": "true: public subnets only, false: private subnets only",
+  "type": "boolean"
+}
    • changedInput schema / properties / vpcNo / description
      Previous value: -"VPC number filter"New value: +"VPC number (from ncloud_hadoop_list_target_vpcs)"
    • removedInput schema / properties / zoneCode
      Removed value: -{
-  "description": "Zone code filter",
-  "type": "string"
-}
    • addedInput schema / required
      Added value: +[
+  "vpcNo",
+  "cloudHadoopImageProductCode"
+]
  2. First observedv1.10.1

TDQS

A3.6/5.0
Behavior3/5

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

The readOnlyHint: true annotation already indicates this is a safe read operation. The description adds the context that it lists subnets 'available for Cloud Hadoop deployment', which is a selection criterion beyond the annotation. No contradictions with annotations.

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 concise sentence with no unnecessary words. It front-loads the action and resource, making it efficient for an agent to parse.

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 simple list tool, the description is complete enough. Required parameters are documented in the schema, safety is covered by the annotation, and no output schema is present. It could mention dependencies on prior calls, but those are already referenced in the parameter descriptions.

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?

The schema description coverage is 100%, with each parameter having a meaningful description, including references to related tools. The description itself does not add extra parameter semantics beyond the schema, which meets the baseline for full coverage.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description 'List subnets available for Cloud Hadoop deployment' clearly states the verb (List), resource (subnets), and context (for Cloud Hadoop deployment). It distinguishes from other target_subnets tools by specifying the Cloud Hadoop service, though it does not explicitly name alternative tools. Purpose is clear and specific.

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 does not provide explicit when-to-use or alternative guidance. However, the parameter descriptions for vpcNo and cloudHadoopImageProductCode reference ncloud_hadoop_list_target_vpcs and ncloud_hadoop_list_image_products, implying that this tool is used after those calls to obtain available subnets. This implicit usage context is useful but not explicit.

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