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

ncloud-mcp-server

by sjk4425
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

ncloud_get_mysql_target_vpcs

Read-only

Identify VPCs available for creating a Cloud DB for MySQL instance. Use this to select a valid target VPC for a specific region.

Instructions

List VPCs available for Cloud DB for MySQL instance creation

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_get_mysql_target_vpcs"
  }
}

Input Schema

NameRequiredDescriptionDefault
regionCodeNoRegion code (e.g. KR, SGN, JPN). Defaults to current region.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.10.1

TDQS

A3.7/5.0
Behavior3/5

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

The annotation readOnlyHint=true already indicates a read-only operation. The description adds context about listing available VPCs, but does not disclose other behavioral traits like pagination, authorization requirements, or response format. The added value is minor.

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, clear sentence of 10 words, front-loaded with the key action and resource. No unnecessary information.

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?

The tool is simple with one optional parameter and no output schema. The description covers the primary purpose but does not mention what the response contains (e.g., VPC IDs or names). Given the complexity, it is adequate but not fully complete.

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% for the single parameter regionCode, and the schema already describes it with examples and default. The tool description adds no additional meaning beyond what the schema provides, so 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 clearly states 'List VPCs available for Cloud DB for MySQL instance creation', specifying the verb 'List', the resource 'VPCs', and the context 'for Cloud DB for MySQL instance creation'. This distinguishes it from sibling tools like ncloud_get_mongodb_target_vpcs.

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 usage when setting up a MySQL instance, but does not explicitly state when to use this tool versus alternatives like ncloud_get_mysql_target_subnets. No prerequisites, exclusions, or scenario guidance is provided.

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