ncloud-gov-mcp-server

ncloud_get_mongodb_target_subnets

Read-only

Provide a Cloud MongoDB instance number to list subnets available for Cloud DB for MongoDB, enabling selection of target subnets for deployment.

Instructions

List subnets available for Cloud DB for MongoDB

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": {
      "cloudMongoDbInstanceNo": "<cloudMongoDbInstanceNo>"
    },
    "name": "ncloud_get_mongodb_target_subnets"
  }
}

Input Schema

Name	Required	Description	Default
`regionCode`	No	Region code (KR, KRS)
`cloudMongoDbInstanceNo`	Yes	Cloud MongoDB instance number

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.1Aug 2, 2026

TDQS

A3.7/5.0

Behavior3/5

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

Annotations declare readOnlyHint=true, and the description's 'List' verb is consistent with that, so there is no contradiction. However, the description adds minimal extra behavior detail beyond the annotation; it does not mention pagination, response format, or instance filtering behavior.

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 or redundant wording. It is front-loaded with the action and resource, making it easy for an agent to quickly grasp the tool's function.

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 relatively simple, with one required parameter, and the schema covers parameter semantics. However, there is no output schema, and the description does not indicate what a successful response contains (e.g., a list of subnet objects with IDs) or that results are scoped to the given MongoDB instance. It is minimally adequate but lacks richer contextual details.

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 (regionCode and cloudMongoDbInstanceNo), giving 100% coverage. The description adds no additional meaning about parameter usage or relationships, so it is at the baseline.

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 the action ('List') and the resource ('subnets available for Cloud DB for MongoDB'), which makes the tool's purpose unmistakable. It also distinguishes itself from sibling tools like ncloud_get_mongodb_target_vpcs and other database-specific target subnet tools.

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 provides no explicit guidance on when to use this tool versus alternatives such as ncloud_get_mongodb_target_vpcs or the generic ncloud_list_subnets. The usage is implied by the name and description, but no exclusions or alternative references are given.

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

Deploy Server