ncp-mcp-server

create_cloud_db

Creates a new Cloud DB instance using parameters for service name, server count, product and image codes, storage type, and optional VPC/subnet information.

Instructions

새로운 Cloud DB 인스턴스를 생성합니다

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": {
      "cloudDBServiceName": "<cloudDBServiceName>",
      "cloudDBServerNamePrefix": "<cloudDBServerNamePrefix>",
      "cloudDBServerCount": "<cloudDBServerCount>",
      "cloudDBProductCode": "<cloudDBProductCode>",
      "cloudDBImageProductCode": "<cloudDBImageProductCode>",
      "dataStorageTypeCode": "<dataStorageTypeCode>"
    },
    "name": "create_cloud_db"
  }
}

Input Schema

Name	Required	Description
`vpcNo`	No	VPC 번호
`subnetNo`	No	서브넷 번호
`cloudDBProductCode`	Yes	상품 코드
`cloudDBServerCount`	Yes	서버 개수
`cloudDBServiceName`	Yes	Cloud DB 서비스 이름
`dataStorageTypeCode`	Yes	스토리지 타입 코드
`cloudDBImageProductCode`	Yes	이미지 상품 코드
`cloudDBServerNamePrefix`	Yes	서버 이름 접두사

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Aug 5, 2026

TDQS

B3.1/5.0

Behavior2/5

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

With no annotations, the description carries the full burden of behavioral disclosure. It only states that it creates an instance, but does not mention potential side effects such as provisioning time, cost implications, required permissions, or whether the operation is asynchronous. This leaves significant ambiguity.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single sentence with no wasted words, which is appropriately concise. However, it is slightly under-specified for a tool with 8 parameters, but the brevity does not harm clarity significantly.

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?

Given the complexity of creating a Cloud DB instance (8 parameters, no output schema), the description is incomplete. It lacks information about expected outcomes, potential errors, or any unique aspects of the process. This leaves the agent without sufficient context to invoke the tool confidently.

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 input schema has full description coverage (100%), so the baseline is 3. The tool description itself adds no parameter semantics beyond what the schema already provides. The schema descriptions are standard and clear, so this dimension is adequately covered by the structured data.

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 'Creates a new Cloud DB instance' in Korean, which is a specific verb+resource combination. It clearly distinguishes from sibling tools like list_cloud_dbs and delete_cloud_db, as creation is a distinct operation.

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

Usage Guidelines2/5

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

No guidance is provided about when to use this tool versus alternatives. While the name implies usage for creating a Cloud DB, there is no explicit context or exclusions, making it unclear whether there are prerequisites or constraints.

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