ncloud-gov-mcp-server

ncloud_export_mongodb_log

Read-only

Export MongoDB server logs to Object Storage for backup and further analysis.

Instructions

Export MongoDB server logs to Object Storage

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>",
      "cloudMongoDbServerInstanceNo": "<cloudMongoDbServerInstanceNo>",
      "bucketName": "<bucketName>",
      "cloudMongoDbExportObjectList": "<cloudMongoDbExportObjectList>"
    },
    "name": "ncloud_export_mongodb_log"
  }
}

Input Schema

Name	Required	Description
`bucketName`	Yes	Object Storage bucket name
`folderPath`	No	Folder path in the bucket
`cloudMongoDbInstanceNo`	Yes	Cloud MongoDB instance number
`cloudMongoDbExportObjectList`	Yes	List of log objects to export
`cloudMongoDbServerInstanceNo`	Yes	Cloud MongoDB server instance number

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.1Aug 2, 2026

TDQS

B3/5.0

Behavior1/5

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

The annotations declare readOnlyHint=true, but the description states the tool exports logs to Object Storage, which creates new objects and implies a write side effect. This contradicts the read-only hint, as the operation modifies the destination bucket state.

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 front-loads the action and destination. No unnecessary words or redundancy.

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 tool has 5 parameters and no output schema, but the description provides no context about return values, asynchronous behavior, or required permissions. It is too minimal to fully inform an agent about the operation's lifecycle.

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 each parameter described (e.g., bucketName, folderPath, cloudMongoDbInstanceNo). The description adds no additional parameter semantics, so the baseline of 3 applies.

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 a specific verb 'Export' with a clear resource ('MongoDB server logs') and destination ('Object Storage'). This clearly distinguishes it from siblings like ncloud_export_mongodb_backup and ncloud_list_mongodb_logs.

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 is provided on when to use this tool versus alternatives. The description does not mention prerequisites, exclusions, or related tools, leaving the agent to infer usage from the name alone.

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

Deploy Server