ncloud-gov-mcp-server

ncloud_delete_product_schema

DestructiveIdempotent

Deletes a user-defined custom schema from Cloud Insight. Provide product name and cw_key, then set confirm=true to permanently remove it.

Instructions

⚠️ Destructive: Delete a user-defined custom schema from Cloud Insight. 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": {
      "prodName": "<prodName>",
      "cw_key": "<cw_key>"
    },
    "name": "ncloud_delete_product_schema"
  }
}

Input Schema

Name	Required	Description
`cw_key`	Yes	Product key (cw_key) of the schema to delete
`confirm`	No	Must be true to actually execute the destructive operation
`prodName`	Yes	Product name of the schema to delete

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.1Aug 2, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already declare destructiveHint and idempotentHint, and the description reinforces this with a '⚠️ Destructive' warning. It adds behavioral value by disclosing the safety guard: the operation only executes when confirm=true.

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 front-loaded sentence that covers the destructive nature, target resource, and required confirm flag. Every word earns its place with no redundancy.

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?

Given the low parameter complexity, full schema coverage, and annotations, the description is nearly complete for a simple destructive delete operation. It covers what is deleted, the destructive implication, and the execution requirement, though it does not mention irreversibility explicitly.

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 fully describes all three parameters with clear definitions, including the confirm default false. The description adds marginal meaning by emphasizing confirm=true, but mostly duplicates schema content.

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 identifies the action (delete), the resource (user-defined custom schema from Cloud Insight), and the context (Cloud Insight). It is distinct from sibling tools like get_product_schema, create_custom_schema, and update_product_schema.

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 usage context by marking the operation as destructive and explicitly instructing that confirm=true is required to execute. It does not enumerate alternatives, but the delete-only scope makes this unnecessary.

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

Deploy Server