ncloud-gov-mcp-server

ncloud_create_postgresql_instance

Create a Cloud DB for PostgreSQL instance on Naver Cloud Government. Use dryRun=true to preview configuration before provisioning.

Instructions

Create a new Cloud DB for PostgreSQL instance. Use dryRun=true to preview without creating.

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": {
      "cloudPostgresqlServiceName": "<cloudPostgresqlServiceName>",
      "vpcNo": "<vpcNo>",
      "subnetNo": "<subnetNo>",
      "cloudPostgresqlDatabaseName": "<cloudPostgresqlDatabaseName>",
      "cloudPostgresqlUserName": "<cloudPostgresqlUserName>",
      "cloudPostgresqlUserPassword": "<cloudPostgresqlUserPassword>",
      "cloudPostgresqlServerNamePrefix": "<cloudPostgresqlServerNamePrefix>",
      "clientCidr": "<clientCidr>"
    },
    "name": "ncloud_create_postgresql_instance"
  }
}

Input Schema

Name	Required	Description
`isHa`	No	High availability setting (default: true)
`vpcNo`	Yes	VPC number
`dryRun`	No	If true, returns a preview without actually creating the instance
`isBackup`	No	Whether to enable automatic backup
`subnetNo`	Yes	Subnet number
`backupTime`	No	Backup time (HH:mm format)
`clientCidr`	Yes	Client CIDR for access control
`isMultiZone`	No	Whether to enable multi-zone high availability
`engineVersionCode`	No	PostgreSQL engine version code (required for Gen3/KVM)
`isAutomaticBackup`	No	Whether to enable automatic backup scheduling
`secondarySubnetNo`	No	Secondary subnet number (required when isMultiZone is true)
`cloudPostgresqlPort`	No	PostgreSQL port number (default: 5432)
`dataStorageTypeCode`	No	Data storage type code (SSD \| HDD \| CB2)
`isStorageEncryption`	No	Storage encryption (cannot be changed after creation)
`backupFileStorageCount`	No	Number of backup files to retain (1-30)
`cloudPostgresqlUserName`	Yes	Initial user name
`isBackupFileCompression`	No	Whether to compress backup files
`backupFileRetentionPeriod`	No	Backup retention period in days (1-30)
`cloudPostgresqlProductCode`	No	PostgreSQL server product (spec) code
`cloudPostgresqlServiceName`	Yes	PostgreSQL service name (3-20 chars, lowercase letters and numbers)
`cloudPostgresqlDatabaseName`	Yes	Initial database name
`cloudPostgresqlUserPassword`	Yes	Initial user password
`cloudPostgresqlImageProductCode`	No	PostgreSQL image product code
`cloudPostgresqlServerNamePrefix`	Yes	Server name prefix

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.1Aug 2, 2026

TDQS

A3.7/5.0

Behavior3/5

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

The annotation only includes destructiveHint=false. The description adds the dryRun preview behavior, which is helpful and not redundant with annotations. However, it does not disclose other behavioral traits such as required permissions, cost implications, or that certain settings (e.g., storage encryption) are immutable after creation—these are only in schema descriptions.

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 exactly two sentences, with no wasted words. It front-loads the core purpose and adds the dryRun tip efficiently.

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?

Given the 24-parameter schema with 100% coverage, the description doesn't need to repeat parameter details. However, it lacks high-level context about dependencies (e.g., secondarySubnetNo when isMultiZone is true) or return values, and there is no output schema. The description is minimal but adequate when combined with the schema.

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%, so the baseline is 3. The description only mentions dryRun, which is already fully described in the schema ('If true, returns a preview without actually creating the instance'), adding no new semantic value for parameters.

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 'Create a new Cloud DB for PostgreSQL instance' with a specific verb and resource, clearly distinguishing this creation action from sibling tools like create_read_replica or delete. The dryRun mention adds further clarity about its behavior.

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 only usage guidance is 'Use dryRun=true to preview without creating,' which provides a useful preview option. However, it does not explain when to use this tool versus alternatives (e.g., creating a read replica) or specify exclusion criteria. The guidance is implied rather than explicit.

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

Deploy Server