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

ncloud-gov-mcp-server

by sjk4425
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

ncloud_hadoop_list_target_subnets

Read-only

List subnets available for Cloud Hadoop deployment. Filter by VPC number, zone code, or region to find suitable network targets.

Instructions

List subnets available for Cloud Hadoop deployment

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "ncloud_hadoop_list_target_subnets"
  }
}

Input Schema

NameRequiredDescriptionDefault
vpcNoNoVPC number filter
zoneCodeNoZone code filter
regionCodeNoRegion code

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

A4.2/5.0
Behavior4/5

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

The readOnlyHint annotation already covers safety. The description adds behavioral context by specifying that returned subnets are filtered by Hadoop compatibility, which is beyond the annotation. It does not disclose pagination or response structure, but for a simple list tool this is acceptable.

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 filler. Every word adds value, front-loading the verb and resource.

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 read-only list operation with three optional filters and no output schema, the description and schema together provide sufficient context to invoke the tool correctly. It lacks details about the response format, but that is not critical for a list operation.

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%, with each parameter (vpcNo, zoneCode, regionCode) having a clear description. The tool description does not add further parameter details, but the baseline is met because the schema fully documents the parameters.

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 uses a specific verb 'List' with the resource 'subnets' and adds the scope 'available for Cloud Hadoop deployment', clearly distinguishing it from generic subnet tools and the sibling ncloud_hadoop_list_target_vpcs. It precisely answers what the tool does.

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 phrase 'available for Cloud Hadoop deployment' provides clear context that this tool is for selecting subnets when deploying Hadoop, setting it apart from general subnet listing tools. However, it does not explicitly state alternatives or exclusions, so it stops short of full when-to-use guidance.

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