Skip to main content
Glama
sjk4425

ncloud-mcp-server

by sjk4425

ncloud_create_postgresql_instance

Provision a new Cloud DB for PostgreSQL instance on Naver Cloud Platform. Use dryRun to validate configuration without actual creation.

Instructions

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

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
isHaNoHigh availability setting (default: true)
vpcNoYesVPC number
dryRunNoIf true, returns a preview without actually creating the instance
isBackupNoWhether to enable automatic backup
subnetNoYesSubnet number
backupTimeNoBackup time (HH:mm format)
clientCidrYesClient CIDR for access control
isMultiZoneNoWhether to enable multi-zone high availability
engineVersionCodeNoPostgreSQL engine version code (required for Gen3/KVM)
isAutomaticBackupNoWhether to enable automatic backup scheduling
secondarySubnetNoNoSecondary subnet number (required when isMultiZone is true)
cloudPostgresqlPortNoPostgreSQL port number (default: 5432)
dataStorageTypeCodeNoData storage type code (SSD | HDD | CB2)
isStorageEncryptionNoStorage encryption (cannot be changed after creation)
backupFileStorageCountNoNumber of backup files to retain (1-30)
cloudPostgresqlUserNameYesInitial user name
isBackupFileCompressionNoWhether to compress backup files
backupFileRetentionPeriodNoBackup retention period in days (1-30)
cloudPostgresqlProductCodeNoPostgreSQL server product (spec) code
cloudPostgresqlServiceNameYesPostgreSQL service name (3-20 chars, lowercase letters and numbers)
cloudPostgresqlDatabaseNameYesInitial database name
cloudPostgresqlUserPasswordYesInitial user password
cloudPostgresqlImageProductCodeNoPostgreSQL image product code
cloudPostgresqlServerNamePrefixYesServer name prefix
Behavior3/5

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

Annotation already indicates non-destructive. Description adds dry-run preview capability, which hints at safety. However, no disclosure of async nature, provisioning time, or required permissions. With annotations covering safety, the description adds minimal additional transparency.

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?

Two concise sentences with no filler. Action and key feature (dry-run) are front-loaded.

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?

For a 24-parameter creation tool, the description is too brief. It does not explain what happens upon successful creation (no output schema, so response expectation is unclear). No prerequisites or behavioral notes beyond dry-run. Leaves gaps for the agent.

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 covers 100% of parameters with descriptions, so description adds no extra meaning beyond the schema. The mention of dryRun in the description is redundant with the schema.

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?

Description clearly states 'Create a new Cloud DB for PostgreSQL instance', with a specific verb and resource. It distinguishes from numerous sibling tools (e.g., create_mysql_instance) by specifying PostgreSQL. The dry-run preview adds detail.

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?

No explicit when-to-use or alternatives provided. The description only states the action without guiding the agent on prerequisites or when not to use. The agent must infer from the tool name and sibling context.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/sjk4425/ncloud-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server