ncloud-gov-mcp-server

ncloud_functions_delete_package

DestructiveIdempotent

Delete a Cloud Functions package permanently. Set confirm=true to execute the destructive operation.

Instructions

⚠️ Destructive: Permanently delete a Cloud Functions package. 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>"
    },
    "name": "ncloud_functions_delete_package"
  }
}

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.1Aug 2, 2026

TDQS

A4.4/5.0

Behavior5/5

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

Beyond the annotations (destructiveHint=true), the description adds critical behavioral context: the deletion is permanent and requires explicit confirmation (confirm=true). This goes beyond what annotations alone convey, and there is no contradiction with the annotations.

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 with a clear warning emoji, concise action statement, and explicit execution requirement. Every word earns its place, with no filler.

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 delete tool with full schema coverage and annotations, the description covers the essential action and prerequisite. It lacks information about potential side effects (e.g., whether deleting a package also deletes its actions/triggers), but this is not strictly required given the tool's simplicity and available structured metadata.

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%, so the baseline is 3. The description mentions 'confirm=true' but this only repeats what the schema already states in the confirm parameter's description. It adds no new semantic information beyond the structured schema.

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 states the verb 'delete' and resource 'Cloud Functions package', with the clarifying qualifier 'permanently'. It clearly distinguishes this tool from sibling delete tools by specifying the target resource (package vs. action, trigger, etc.).

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 context for use: it is a destructive operation requiring confirm=true to execute. It does not explicitly name alternatives or when-not-to-use, but the specific resource and confirmation requirement give sufficient usage guidance for this simple deletion tool.

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

Deploy Server