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

ncloud-gov-mcp-server

by sjk4425
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

ncloud_get_postgresql_target_vpcs

Read-only

Lists VPCs available for Cloud DB for PostgreSQL instance creation. Use this to select the target VPC.

Instructions

List VPCs available for Cloud DB for PostgreSQL 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_postgresql_target_vpcs"
  }
}

Input Schema

NameRequiredDescriptionDefault
regionCodeNoRegion code (KR, KRS). Defaults to current region.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

A4.1/5.0
Behavior3/5

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

The readOnlyHint annotation already signals this is a safe read operation. The description adds the context that it only returns VPCs eligible for PostgreSQL instance creation, which is useful, but does not describe return format or pagination. A baseline score of 3 is appropriate given annotation coverage.

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, front-loaded sentence that conveys the purpose without any filler. Every word adds value.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

This is a low-complexity list tool with one optional parameter, clear schema documentation, and a read-only annotation. The description sufficiently conveys what the tool does and when it would be used, making the context complete without needing to describe return values.

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%: regionCode is documented with valid values (KR, KRS) and a default. The description adds no additional parameter semantics, but the schema already fully explains the parameter, so the baseline of 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 available for Cloud DB for PostgreSQL instance creation'), clearly distinguishing it from sibling tools like target_subnets or target_vpcs for other database services.

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 DB for PostgreSQL instance creation' implies this should be used to fetch candidate VPCs before creating a PostgreSQL instance. It does not explicitly mention exclusions or name alternative tools, but the context is clear.

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