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

ncloud-mcp-server

by sjk4425
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

ncloud_get_mongodb_target_vpcs

Read-only

List VPCs available for Cloud DB for MongoDB, helping you select the target network for database deployment.

Instructions

List VPCs available for Cloud DB for MongoDB

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

Input Schema

NameRequiredDescriptionDefault
regionCodeNoRegion code (e.g., KR, JPN, SGN)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.10.1

TDQS

B3.4/5.0
Behavior2/5

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

Annotations already indicate readOnlyHint=true, so the description adds no behavioral context beyond that. It does not disclose whether the list is full or filtered, if authorization is needed, or what happens with the optional regionCode parameter. Minimal extra 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, clear sentence with no redundant information. Efficiently communicates the core purpose.

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

Completeness2/5

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

The description is too brief for a listing tool with no output schema. It fails to specify the scope of VPCs (all user VPCs? target-compatible VPCs?) or any filtering logic. The optional regionCode parameter's effect on results is unclear.

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% with regionCode already described. The description 'available for Cloud DB for MongoDB' provides context but does not add parameter-specific meaning beyond the schema.

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 VPCs available for Cloud DB for MongoDB' clearly states the verb ('List'), resource ('VPCs'), and specific context ('for Cloud DB for MongoDB'), effectively differentiating it from sibling tools like ncloud_get_mysql_target_vpcs and ncloud_get_cache_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?

No explicit guidance on when to use this tool or alternatives. While the description implies use for MongoDB VPC needs, it does not mention when not to use it or direct to siblings for other databases.

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