Skip to main content
Glama

ncloud_create_mysql_instance

Create a Cloud DB for MySQL instance on Naver Cloud Government. Use dryRun to preview settings without provisioning.

Instructions

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

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
isHaNoHigh availability (default: true). If true, creates Standby Master (2 servers). If false, isMultiZone/standbyMasterSubnetNo are ignored.
vpcNoYesVPC number (getCloudMysqlTargetVpcList)
dryRunNoIf true, returns a preview without actually creating the instance
hostIpYesHost IP for MySQL access (e.g. '%' for all, '1.1.1.1', '1.1.1.%', '1.1.1.0/24'). Use '%25' for '%' in GET requests.
isBackupNoBackup enabled (default: true). Fixed to true when isHa=true.
subnetNoYesSubnet number for primary NIC (getCloudMysqlTargetSubnetList)
backupTimeNoBackup time in HH:mm format (e.g. '02:00'). Required when isBackup=true and isAutomaticBackup=false.
regionCodeNoRegion code (KR, KRS). Defaults to first region.
isMultiZoneNoMulti-zone HA (default: false). Required when isHa=true. Places Master and Standby in different zones.
cloudMysqlPortNoMySQL TCP port (default: 3306, range: 10000-20000). Cannot change after creation.
engineVersionCodeNoDB engine version code (getCloudMysqlImageProductList). Defaults to latest version.
isAutomaticBackupNoAutomatic backup time scheduling (default: true). If true, backupTime cannot be specified.
cloudMysqlUserNameYesDB user account ID (3-16 chars, starts with letter, allows letters/numbers/'-'/'_')
isDeleteProtectionNoCluster deletion protection (default: false). If true, cluster cannot be deleted.
isPrivateSubDomainNoUse private sub-domain (true/false)
dataStorageTypeCodeNoData storage type. G2 default: SSD, G3 default: CB2. Cannot change after creation.
isStorageEncryptionNoStorage encryption (default: false). Only available when isHa=true. Cannot change after creation.
cloudMysqlProductCodeNoMySQL server product (spec) code (getCloudMysqlProductList). Defaults to minimum spec.
cloudMysqlServiceNameYesMySQL service name (3-30 chars, letters, numbers, Korean, '-')
standbyMasterSubnetNoNoSubnet for Standby Master server. Required when isMultiZone=true. Must be different zone from primary subnet.
cloudMysqlDatabaseNameYesInitial database name (1-30 chars, starts with letter)
cloudMysqlUserPasswordYesDB user password (8-20 chars, must include letter+number+special char)
privateSubDomainPrefixNoPrivate sub-domain prefix (3-15 chars). Required when isPrivateSubDomain=true.
backupFileRetentionPeriodNoBackup retention period in days (default: 1). Only InnoDB tables supported.
cloudMysqlImageProductCodeNoMySQL image product code (getCloudMysqlImageProductList)
cloudMysqlServerNamePrefixYesServer name prefix (3-20 chars, starts with letter, ends with letter/number, allows '-')
Behavior3/5

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

Annotations only provide destructiveHint=false. The description adds the dryRun capability which is not in annotations, giving a preview without creation. However, it does not disclose asynchronous behavior, expected response, or any side effects beyond the creation itself.

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 short sentences that are front-loaded with the action and resource. No unnecessary words.

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?

Despite the comprehensive schema, the description lacks context about the operation's outcome, such as return values, eventual consistency, or how to monitor creation progress. With no output schema, this leaves a gap for a tool with 26 parameters.

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?

The schema covers 100% of parameters with descriptions, including dryRun. The description repeats the dryRun behavior without adding new meaning beyond the schema, so it scores at the baseline of 3.

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 action (create) and the resource (Cloud DB for MySQL instance), distinguishing it from other database creation tools by naming MySQL specifically. The verb+resource pattern is specific and unambiguous.

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 does not explicitly state when to use this tool over alternatives such as ncloud_create_postgresql_instance or ncloud_create_mysql_slave. It only implies usage through the tool name and the dryRun preview tip, which is more of a behavioral hint than usage guidance.

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-gov-mcp-server'

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