ncloud-gov-mcp-server

ncloud_functions_delete_action

DestructiveIdempotent

Delete a Cloud Functions action permanently. Requires confirm=true to execute the destructive operation.

Instructions

⚠️ Destructive: Permanently delete a Cloud Functions action. 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": {
      "packageName": "<packageName>",
      "actionName": "<actionName>"
    },
    "name": "ncloud_functions_delete_action"
  }
}

Input Schema

Name	Required	Description	Default
`confirm`	No	Must be true to actually execute the destructive operation
`platform`	No	Platform type (default: vpc)	vpc
`actionName`	Yes	Name of the action to delete
`packageName`	Yes	Package name containing the action

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?

The description adds behavioral context beyond the annotations by emphasizing 'Permanently' and specifying 'Set confirm=true to execute.' This discloses the confirmation requirement and irreversibility, which is valuable for an agent deciding to invoke the tool.

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 just two sentences, front-loaded with the destructive warning and a clear verb. Every word earns its place without redundancy or digression.

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 simple destructive delete operation, the combination of annotations (destructiveHint, idempotentHint) and full schema coverage provides sufficient context. The description covers the critical confirm gate. It doesn't elaborate on return values, but that is not essential for this type of operation.

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 has 100% coverage with descriptions for all parameters. The description mentions confirm, but the schema already explains that confirm must be true to execute. Thus, the description adds little meaning beyond the structured parameter definitions.

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 specific action: 'Permanently delete a Cloud Functions action.' This uses a precise verb and resource, distinguishing it from sibling tools like ncloud_functions_create_action or ncloud_functions_list_actions.

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 gives clear context: it is destructive and requires confirm=true to execute. While it doesn't explicitly mention alternatives or exclusions, the purpose is unambiguous for deletion tasks, and the confirm=true instruction provides practical usage guidance.

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

Deploy Server