ncloud-gov-mcp-server

ncloud_export_postgresql_backup

Read-only

Export a Cloud DB for PostgreSQL backup file to Object Storage. Specify instance, backup file name, and target bucket to transfer the backup for archival or recovery.

Instructions

Export a Cloud DB for PostgreSQL backup file to Object Storage. Use ncloud_list_postgresql_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": {
      "cloudPostgresqlInstanceNo": "<cloudPostgresqlInstanceNo>",
      "fileName": "<fileName>",
      "bucketName": "<bucketName>"
    },
    "name": "ncloud_export_postgresql_backup"
  }
}

Input Schema

Name	Required	Description
`fileName`	Yes	Backup file name to export (from ncloud_list_postgresql_backup_details)
`bucketName`	Yes	Object Storage bucket name to export to
`folderPath`	No	Folder path within the bucket (e.g. 'postgresql-backups/daily'). If omitted, exports to bucket root.
`regionCode`	No	Region code (default: current region)
`cloudPostgresqlInstanceNo`	Yes	Cloud PostgreSQL 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 description directly contradicts the annotation 'readOnlyHint: true'. Exporting a backup to Object Storage is a write operation with side effects, not a read-only operation. The annotation claims read-only while the description says 'Export', so the contradiction is severe.

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 only two sentences, with the primary verb and resource front-loaded. Every word earns its place, and the reference to the listing tool is valuable without being verbose.

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 sparse for an export operation with no output schema. It does not mention whether the operation is asynchronous, what the return value looks like, or any required permissions or side effects. The contradiction with the annotation also reduces trust in the completeness.

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 all parameters having descriptions. The tool description adds no extra parameter semantics beyond the schema, but the schema itself is sufficiently descriptive. Baseline 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 states a specific action ('Export'), a specific resource ('Cloud DB for PostgreSQL backup file'), and a destination ('Object Storage'). It also references a sibling tool for obtaining file names, which helps distinguish it from similar export tools for other database types.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description explicitly instructs the user to use 'ncloud_list_postgresql_backup_details' to get available file names, providing clear prerequisite guidance. It does not explicitly mention when not to use it, but the tool name and context make the database type clear.

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

Deploy Server