Skip to main content
Glama
sjk4425

ncloud-mcp-server

by sjk4425
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

ncloud_functions_delete_action

DestructiveIdempotent

Permanently delete a Cloud Functions action by providing its name and package. Set confirm=true to execute the destructive operation.

Instructions

⚠️ Destructive: Permanently delete a Cloud Functions action. Set confirm=true to execute.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
confirmNoMust be true to actually execute the destructive operation
platformNoPlatform (default: vpc). Singapore/Japan regions support vpc only.vpc
actionNameYesName of the action to delete
packageNameNoPackage name ('-' = unpackaged action)-

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv1.15.0
    • addedInput schema / properties / packageName / default
      Added value: +"-"
    • changedInput schema / properties / packageName / description
      Previous value: -"Package name containing the action"New value: +"Package name ('-' = unpackaged action)"
    • changedInput schema / properties / platform / description
      Previous value: -"Platform type (default: vpc)"New value: +"Platform (default: vpc). Singapore/Japan regions support vpc only."
    • changedInput schema / required
      Previous value: -[
-  "packageName",
-  "actionName"
-]New value: +[
+  "actionName"
+]
  2. First observedv1.10.1

TDQS

A4/5.0
Behavior4/5

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

Annotations already flag destructiveHint, and the description adds useful behavioral context: the deletion is permanent and guarded by an explicit confirm flag. It aligns with idempotentHint (no contradiction) and clarifies that the operation is irreversible.

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?

Two short sentences front-load the safety warning, state the operation, and give the required guard. No filler or repetition.

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 single-resource delete, the combination of warning, permanence, and confirm gate covers what an agent needs, with parameter details fully handled by the schema. It could mention what happens to linked packages/triggers, but this is not a critical gap.

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 applies. The description's only parameter-related statement, 'Set confirm=true', merely echoes the schema's confirm description without adding new meaning.

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?

Description states a specific verb ('delete') and resource ('Cloud Functions action'), making the tool's scope unmistakable and distinguishing it from sibling delete tools such as ncloud_functions_delete_package or ncloud_functions_delete_trigger.

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 intent to use this when deleting an action is implied, and 'Set confirm=true to execute' provides an invocation requirement, but there is no explicit when/when-not guidance or mention of alternatives. An agent must infer the difference from the name/schema rather than the description.

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

Deploy Server

Other Tools