ncloud-gov-mcp-server

ncloud_delete_postgresql_databases

DestructiveIdempotent

Delete databases from a Cloud DB for PostgreSQL instance. Requires confirm=true to execute this destructive operation.

Instructions

⚠️ Destructive: Delete databases from a Cloud DB for PostgreSQL instance. Set confirm=true to execute.

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": {
      "cloudPostgresqlInstanceNo": "<cloudPostgresqlInstanceNo>",
      "cloudPostgresqlDatabaseList": "<cloudPostgresqlDatabaseList>"
    },
    "name": "ncloud_delete_postgresql_databases"
  }
}

Input Schema

Name	Required	Description
`confirm`	No	Must be true to actually execute the destructive operation
`cloudPostgresqlInstanceNo`	Yes	Cloud PostgreSQL instance number
`cloudPostgresqlDatabaseList`	Yes	List of databases to delete

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.1Aug 2, 2026

TDQS

A4/5.0

Behavior4/5

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

Annotations already declare destructiveHint and idempotentHint, but the description adds critical behavioral context: the operation requires confirm=true to execute, reinforcing the destructive nature. This goes beyond the annotations by explaining the safety mechanism, which is valuable for an agent to avoid accidental data loss.

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 extremely concise: one short sentence with a clear warning prefix. It front-loads the destructive warning and essential execution requirement, with no redundant words.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a destructive operation with no output schema, the description adequately covers key aspects: destructive warning, confirm flag, and scope (databases from an instance). It doesn't explain return values or prerequisites, but those are not critical for a delete operation, and the schema handles parameter documentation.

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 provides 100% coverage of all three parameters (confirm, cloudPostgresqlInstanceNo, cloudPostgresqlDatabaseList) with descriptions. The description only reiterates the confirm=true requirement, which is already in the schema, adding no new semantic detail.

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 (delete databases) and the target resource (Cloud DB for PostgreSQL instance), distinguishing it from sibling tools like delete_postgresql_instance or delete_postgresql_users. The verb 'Delete' and resource scope are 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 implies usage for deleting databases from a PostgreSQL instance but does not explicitly compare with alternatives or state exclusions. The confirm=true instruction provides operational guidance, but the 'when to use vs. alternatives' aspect is only inferred from the name and context.

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

Deploy Server