ncloud-gov-mcp-server

ncloud_list_mongodb_instances

Read-only

List Cloud DB for MongoDB instances in the current region. Filter by service name or instance numbers and control results with pagination.

Instructions

List all Cloud DB for MongoDB instances in the current region

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

Input Schema

Name	Required	Description
`pageNo`	No	Page number for pagination
`pageSize`	No	Page size for pagination
`cloudMongoDbServiceName`	No	Filter by MongoDB service name
`cloudMongoDbInstanceNoList`	No	Filter by MongoDB instance numbers

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.1Aug 2, 2026

TDQS

A4/5.0

Behavior4/5

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

The phrase 'all' and 'current region' disclose behavioral scope—returns all instances in the current region—beyond the readOnlyHint annotation. This adds useful context without contradicting the annotation, though pagination behavior is left to the schema.

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 sentence with a front-loaded action verb 'List' and a direct object. No filler or redundant information.

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 list tool with no output schema, the description adequately sets expectations for returning MongoDB instances in the current region. Pagination and filters are documented in the schema, so overall completeness is strong for a simple read operation.

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 schema covers all four parameters with clear descriptions (pagination and filters). The description does not add meaning beyond the schema, so it meets the baseline of 3.

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 the explicit verb 'List' with the resource 'Cloud DB for MongoDB instances' and scopes it to 'current region', clearly distinguishing it from sibling tools like ncloud_get_mongodb_instance_detail and ncloud_list_mongodb_users.

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 implies usage for enumerating MongoDB instances in the current region but does not mention alternatives, when-not-to-use, or exclusion scenarios. No explicit guidance is given beyond the inherent list operation.

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

Deploy Server