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

ncloud-mcp-server

by sjk4425
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

ncloud_get_mongodb_target_subnets

Read-only

Find available subnets for Cloud DB for MongoDB using the instance number. Specify region code optionally to filter results and choose the right subnet for your 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

NameRequiredDescriptionDefault
regionCodeNoRegion code (e.g., KR, JPN, SGN)
cloudMongoDbInstanceNoYesCloud MongoDB instance number

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.10.1

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, and the description confirms it is a list operation. However, it does not disclose any additional behavioral traits such as pagination, required instance existence, or response format. With annotations covering the safety profile, the description adds minimal value.

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?

A single concise sentence with no wasted words. It is front-loaded and efficiently communicates the tool's purpose.

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?

For a simple read-only listing tool with no output schema, the description is adequate but does not specify what information the subnets will contain (e.g., IDs, names). Given the tool's low complexity and available annotations, it is minimally 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 description coverage is 100% with both parameters described (regionCode and cloudMongoDbInstanceNo). The tool description adds no parameter-level information, so it meets the baseline for high coverage.

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 'List subnets available for Cloud DB for MongoDB' clearly states a specific verb ('List') and resource ('subnets available for Cloud DB for MongoDB'), distinguishing it from sibling tools like ncloud_get_mongodb_target_vpcs and ncloud_list_mongodb_instances.

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 on when to use this tool versus alternatives such as ncloud_get_mongodb_target_vpcs or other subnet listing tools. The description only states the action, 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

Other Tools