ncloud-gov-mcp-server

ncloud_delete_fabric_cluster

DestructiveIdempotent

Permanently delete a fabric cluster. Set confirm=true to execute the destructive operation.

Instructions

⚠️ Destructive: Permanently delete a fabric cluster. 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": {
      "fabricClusterNo": "<fabricClusterNo>"
    },
    "name": "ncloud_delete_fabric_cluster"
  }
}

Input Schema

Name	Required	Description	Default
`confirm`	No	Must be true to actually execute the destructive operation
`fabricClusterNo`	Yes	Fabric cluster number to delete

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.1Aug 2, 2026

TDQS

A4.1/5.0

Behavior4/5

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

With annotations already marking destructiveHint and idempotentHint, the description adds valuable behavioral context by stating the operation is destructive, permanent, and gated by the confirm parameter. This goes beyond the annotation flags and clarifies the execution prerequisite.

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 one sentence, front-loaded with the destructive warning, and packs essential information (permanence, confirmation requirement) with zero wasted words.

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

Completeness5/5

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

For a delete tool with simple parameters and no output schema, the description covers all necessary context: the action, the destructive/permanent nature, and the required confirm flag. It is fully sufficient for an agent to select and invoke the tool correctly.

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 both confirm and fabricClusterNo having clear descriptions. The description reiterates the confirm requirement but doesn't add new parameter meaning beyond what the schema already provides, keeping it at the high-coverage baseline.

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 ('delete') and the resource ('fabric cluster'), with the important qualifier 'permanently' indicating irreversibility. It is specific enough to distinguish from sibling tools by resource type, though it doesn't explicitly name alternatives.

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

Usage Guidelines4/5

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

The description provides clear guidance on how to execute the operation ('Set confirm=true to execute'), which is an essential usage condition. It does not mention when to use this over other delete tools, but the resource-specific naming and the explicit confirmation requirement give sufficient context.

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

Deploy Server