ncloud-gov-mcp-server

ncloud_get_postgresql_target_subnets

Read-only

List available subnets for creating a Cloud DB for PostgreSQL instance. Specify the instance number to retrieve target subnets.

Instructions

List subnets available for Cloud DB for PostgreSQL instance creation within a specific PostgreSQL instance

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "cloudPostgresqlInstanceNo": "<cloudPostgresqlInstanceNo>"
    },
    "name": "ncloud_get_postgresql_target_subnets"
  }
}

Input Schema

Name	Required	Description	Default
`regionCode`	No	Region code (KR, KRS). Defaults to current region.
`cloudPostgresqlInstanceNo`	Yes	Cloud PostgreSQL instance number

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.1Aug 2, 2026

TDQS

B3.4/5.0

Behavior3/5

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

The readOnlyHint annotation already declares this as a safe read operation, so the description doesn't need to repeat that. It adds some context by specifying subnets are for instance creation, but doesn't disclose filtering behavior, pagination, or response format. This is minimal additional value beyond 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 sentence of 14 words, front-loaded with the action 'List subnets'. It contains no redundant words or filler, making it highly concise and scannable.

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 operation with one required parameter and one optional parameter, the description conveys the core purpose effectively. The ambiguity around 'within a specific PostgreSQL instance' and lack of mention of response characteristics leave a small gap, but the tool is simple enough that this is largely sufficient.

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 input schema provides descriptions for both parameters with 100% coverage, so the description doesn't need to elaborate. It doesn't add any semantic nuance beyond what the schema already states, such as the relationship between the instance number and the subnets returned.

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 uses the specific verb 'List' and identifies the resource as 'subnets available for Cloud DB for PostgreSQL instance creation'. It distinguishes from sibling tools by naming PostgreSQL. However, the phrase 'within a specific PostgreSQL instance' is ambiguous because subnets aren't within an instance; it may mean subnets associated with a specific instance, which slightly detracts from clarity.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance is provided on when to use this tool versus similar sibling tools like ncloud_get_postgresql_target_vpcs or ncloud_get_mysql_target_subnets. There are no alternatives, exclusions, or preconditions mentioned, leaving the agent to infer usage context.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server