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

ncloud-mcp-server

by sjk4425
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

ncloud_hadoop_list_target_vpcs

Read-only

Identify VPCs eligible for Cloud Hadoop deployment. Specify a region code to retrieve the list of available VPCs for your Hadoop cluster.

Instructions

List VPCs 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_vpcs"
  }
}

Input Schema

NameRequiredDescriptionDefault
regionCodeNoRegion code

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.10.1

TDQS

A4/5.0
Behavior3/5

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

The readOnlyHint annotation already indicates a safe read operation. The description adds that the result is filtered to VPCs available for Hadoop deployment, which is useful behavioral context. However, it does not clarify what 'available' means (e.g., region eligibility, zone support) or describe return format/pagination, so the bar is only partially met.

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 seven-word sentence, front-loaded with the verb 'List,' and contains zero redundant information. Every word earns its place.

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 one-parameter, read-only list tool, the description adequately conveys purpose and scope. It lacks an explicit note that regionCode is optional or details on what makes a VPC 'available,' but the low complexity and readOnlyHint annotation make the description sufficient for selection and invocation.

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 sole parameter regionCode is fully described in the input schema as 'Region code' (100% coverage). The description adds no parameter-specific detail beyond the schema, so the baseline 3 applies.

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') and resource ('VPCs'), and clearly scopes it to 'available for Cloud Hadoop deployment.' This distinguishes it from the general ncloud_list_vpcs and related Hadoop target-list tools (e.g., ncloud_hadoop_list_target_subnets).

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' clearly implies this tool is for selecting VPCs when provisioning Hadoop clusters, providing clear context. It does not explicitly name alternatives or exclusions, but the Hadoop-specific scoping makes the intended usage evident.

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