ncloud-gov-mcp-server

ncloud_export_mssql_backup

Read-only

Export Cloud DB for MSSQL backup files to Object Storage. Retrieve available file names via ncloud_list_mssql_backup_details.

Instructions

Export Cloud DB for MSSQL backup files to Object Storage. Use ncloud_list_mssql_backup_details to get available file names.

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": {
      "cloudMssqlInstanceNo": "<cloudMssqlInstanceNo>",
      "cloudMssqlServerInstanceNo": "<cloudMssqlServerInstanceNo>",
      "bucketName": "<bucketName>",
      "cloudMssqlExportObjectList": "<cloudMssqlExportObjectList>"
    },
    "name": "ncloud_export_mssql_backup"
  }
}

Input Schema

Name	Required	Description
`bucketName`	Yes	Object Storage bucket name to export to
`folderPath`	No	Folder path within the bucket. If omitted, exports to bucket root.
`cloudMssqlInstanceNo`	Yes	Cloud MSSQL instance number
`cloudMssqlExportObjectList`	Yes	List of backup objects to export
`cloudMssqlServerInstanceNo`	Yes	Cloud MSSQL server instance number

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.1Aug 2, 2026

TDQS

B3.4/5.0

Behavior1/5

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

The annotation readOnlyHint=true contradicts the description's 'Export... to Object Storage', which implies a side-effectful write operation. The description adds no further context about permissions, asynchronous execution, or the actual impact, leaving the contradiction unresolved.

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 two sentences long and front-loaded with the primary function. The second sentence provides actionable guidance without any fluff or repetition.

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 omits critical behavioral details such as whether the export is asynchronous, what the response contains, or any required preconditions (e.g., bucket existence). Combined with the contradictory readOnlyHint annotation, the tool is under-described for an agent to fully understand its side effects.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the baseline is 3. The description adds value by connecting the cloudMssqlExportObjectList parameter to ncloud_list_mssql_backup_details, explaining where to obtain the file names for that list.

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 tool 'Exports Cloud DB for MSSQL backup files to Object Storage.' It uses a specific verb (export), resource (MSSQL backup files), and target (Object Storage), which distinguishes it from similar tools like ncloud_export_mssql_log.

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 provides a helpful prerequisite by directing users to ncloud_list_mssql_backup_details for available file names, but it does not explicitly state when to use this tool over alternatives (e.g., ncloud_export_mssql_log) or mention any exclusions.

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

Deploy Server