ncloud-mcp-server

ncloud_list_mongodb_backups

Read-only

List backups for a Cloud DB for MongoDB instance by supplying the instance number, enabling quick review of available backup data for restoration or management.

Instructions

List backups for a Cloud DB for MongoDB 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": {
      "cloudMongoDbInstanceNo": "<cloudMongoDbInstanceNo>"
    },
    "name": "ncloud_list_mongodb_backups"
  }
}

Input Schema

Name	Required	Description	Default
`cloudMongoDbInstanceNo`	Yes	Cloud MongoDB instance number

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.10.1Jul 29, 2026

TDQS

A3.5/5.0

Behavior2/5

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

The readOnlyHint annotation already communicates that this is a safe read operation. The description adds no further behavioral information, such as whether both manual and automatic backups are listed, pagination behavior, or the structure of the returned data. It essentially restates the tool's static purpose without enriching the agent's understanding.

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 that conveys the core purpose without filler. It is well-structured and immediately understandable.

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 tool with only one parameter and no output schema, the description is minimally viable but lacks detail on what the returned backup list contains or whether there are filtering options. It does not explain the distinction from the backup details tool, leaving some ambiguity for an agent needing to choose the right 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 input schema fully describes the single parameter (cloudMongoDbInstanceNo) with a clear description. The tool description adds no additional parameter-level meaning beyond what the schema provides, so the baseline of 3 is appropriate.

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), the resource (backups), and the scope (Cloud DB for MongoDB instance). It distinguishes itself from sibling tools like ncloud_list_mongodb_backup_details by focusing on backups generally rather than details.

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 by naming the resource, but does not explicitly state when to use this tool over related siblings such as list_mongodb_backup_details or export_mongodb_backup. There is no mention of alternatives or exclusions, leaving the agent to infer the appropriate context.

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

Deploy Server