ncp-mcp-server

delete_cloud_db

Deletes a specified Cloud DB instance from Naver Cloud Platform. Provide the instance number to remove the database.

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": {
      "cloudDBInstanceNo": "<cloudDBInstanceNo>"
    },
    "name": "delete_cloud_db"
  }
}

Input Schema

Name	Required	Description	Default
`cloudDBInstanceNo`	Yes	Cloud DB 인스턴스 번호

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Aug 5, 2026

TDQS

B3.2/5.0

Behavior2/5

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

With no annotations, the description carries full responsibility for behavioral disclosure. It only states 'deletes' without specifying whether deletion is permanent, requires the instance to be stopped, or cascades to associated resources. This is a significant gap for a destructive operation.

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 short sentence that immediately states the action. It is extremely concise and earns a top score for conciseness.

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 simple delete tool, the description is minimal but the lack of any behavioral caveats (e.g., irreversibility, dependencies) leaves it incomplete for an agent evaluating consequences. It does not fully cover the context needed.

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 has 100% coverage for the single parameter, so the description need not add parameter details. However, it adds no extra semantic value beyond the schema, earning the baseline score.

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 uses a specific verb '삭제합니다' (deletes) and clearly identifies the resource as 'Cloud DB 인스턴스', distinguishing it from sibling delete tools for servers, VPCs, subnets, and load balancers. The intent is unambiguous.

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 on when to use this tool, prerequisites, or alternatives. The description simply states the action without any contextual usage direction.

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