Skip to main content
Glama
choec77

NCP MCP Server

by choec77
OverviewSchemaRelated ServersScoreDiscussions
JavaScript
Remote

create_cloud_db

Create new Cloud DB instances on Naver Cloud Platform by specifying service name, server configuration, product codes, and network settings.

Instructions

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

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
cloudDBServiceNameYesCloud DB 서비스 이름
cloudDBServerNamePrefixYes서버 이름 접두사
cloudDBServerCountYes서버 개수
cloudDBProductCodeYes상품 코드
cloudDBImageProductCodeYes이미지 상품 코드
dataStorageTypeCodeYes스토리지 타입 코드
vpcNoNoVPC 번호
subnetNoNo서브넷 번호

Implementation Reference

  • src/index.ts:246-257 (handler)
    Core handler function in NCPClient class that performs the actual Cloud DB creation by making an authenticated GET request to the NCP API endpoint /clouddb/v2/createCloudDBInstance.
    async createCloudDB(params: {
  cloudDBServiceName: string;
  cloudDBServerNamePrefix: string;
  cloudDBServerCount: string;
  cloudDBProductCode: string;
  cloudDBImageProductCode: string;
  dataStorageTypeCode: string;
  vpcNo?: string;
  subnetNo?: string;
}) {
  return await this.request("GET", "/clouddb/v2", "/createCloudDBInstance", params);
}
  • src/index.ts:730-742 (handler)
    MCP tool call dispatcher switch case that handles incoming 'create_cloud_db' tool requests by casting arguments to the correct type and delegating to ncpClient.createCloudDB.
    case "create_cloud_db": {
  const typedArgs = args as {
    cloudDBServiceName: string;
    cloudDBServerNamePrefix: string;
    cloudDBServerCount: string;
    cloudDBProductCode: string;
    cloudDBImageProductCode: string;
    dataStorageTypeCode: string;
    vpcNo?: string;
    subnetNo?: string;
  };
  result = await ncpClient.createCloudDB(typedArgs);
  break;
  • src/index.ts:538-551 (schema)
    Input schema definition for the 'create_cloud_db' tool, specifying parameters and required fields, matching the handler function signature.
    inputSchema: {
  type: "object",
  properties: {
    cloudDBServiceName: { type: "string", description: "Cloud DB 서비스 이름" },
    cloudDBServerNamePrefix: { type: "string", description: "서버 이름 접두사" },
    cloudDBServerCount: { type: "string", description: "서버 개수" },
    cloudDBProductCode: { type: "string", description: "상품 코드" },
    cloudDBImageProductCode: { type: "string", description: "이미지 상품 코드" },
    dataStorageTypeCode: { type: "string", description: "스토리지 타입 코드" },
    vpcNo: { type: "string", description: "VPC 번호" },
    subnetNo: { type: "string", description: "서브넷 번호" },
  },
  required: ["cloudDBServiceName", "cloudDBServerNamePrefix", "cloudDBServerCount", "cloudDBProductCode", "cloudDBImageProductCode", "dataStorageTypeCode"],
},
  • src/index.ts:535-552 (registration)
    Registration of the 'create_cloud_db' tool in the MCP server's tool list response, including name, description, and schema.
    {
  name: "create_cloud_db",
  description: "새로운 Cloud DB 인스턴스를 생성합니다",
  inputSchema: {
    type: "object",
    properties: {
      cloudDBServiceName: { type: "string", description: "Cloud DB 서비스 이름" },
      cloudDBServerNamePrefix: { type: "string", description: "서버 이름 접두사" },
      cloudDBServerCount: { type: "string", description: "서버 개수" },
      cloudDBProductCode: { type: "string", description: "상품 코드" },
      cloudDBImageProductCode: { type: "string", description: "이미지 상품 코드" },
      dataStorageTypeCode: { type: "string", description: "스토리지 타입 코드" },
      vpcNo: { type: "string", description: "VPC 번호" },
      subnetNo: { type: "string", description: "서브넷 번호" },
    },
    required: ["cloudDBServiceName", "cloudDBServerNamePrefix", "cloudDBServerCount", "cloudDBProductCode", "cloudDBImageProductCode", "dataStorageTypeCode"],
  },
},

Tool Definition Quality

C2.9/5.0
Behavior2/5

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

No annotations are provided, so the description carries full burden. It states this is a creation tool, implying a write/mutation operation, but doesn't disclose critical behavioral traits: whether it's idempotent, what permissions are required, if it's asynchronous, potential costs, or error conditions. For a complex infrastructure creation tool with 8 parameters, this is a significant gap in 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?

The description is a single, efficient sentence that states the core purpose without unnecessary words. It's appropriately sized and front-loaded, with every word contributing directly to understanding what the tool does. No fluff or redundant information is present.

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, infrastructure tool), no annotations, and no output schema, the description is insufficient. It doesn't explain what happens after creation, return values, error handling, or dependencies on other resources (like VPC/subnet). For a mutation tool of this complexity, more contextual information is needed to guide proper usage.

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%, with all parameters documented in the schema itself. The description adds no additional parameter information beyond the action of creation. This meets the baseline of 3 since the schema adequately describes each parameter, but the description doesn't provide higher-level context about parameter relationships or usage patterns.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the action ('새로운...생성합니다' - 'creates a new') and resource ('Cloud DB 인스턴스' - 'Cloud DB instance'), making the purpose immediately understandable. However, it doesn't explicitly differentiate from sibling tools like 'create_server' or 'create_vpc', which would require more specific context about what makes a Cloud DB instance distinct from other resources.

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?

The description provides no guidance on when to use this tool versus alternatives. With siblings like 'create_server', 'create_vpc', and 'list_cloud_dbs', there's no indication of prerequisites, dependencies (e.g., needing a VPC/subnet first), or comparative use cases. The agent must infer usage from the tool name alone.

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/choec77/mcp'

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