Skip to main content
Glama
Sign In
ncloud-gov-mcp-server

ncloud-gov-mcp-server

by sjk4425
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

ncloud_functions_unlink_trigger_action

Destructive

Unlink an action from a trigger in Ncloud Functions. Requires confirm=true to execute this destructive change.

Instructions

⚠️ Destructive: Unlink an action from a trigger. 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": {
      "triggerName": "<triggerName>",
      "actionName": "<actionName>"
    },
    "name": "ncloud_functions_unlink_trigger_action"
  }
}

Input Schema

NameRequiredDescriptionDefault
confirmNoMust be true to actually execute the destructive operation
platformNoPlatform type (default: vpc)vpc
actionNameYesAction name in "{packageName}/{actionName}" format
triggerNameYesName of the trigger

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true, and the description reinforces this with '⚠️ Destructive.' Beyond that, it adds critical behavioral context: 'Set confirm=true to execute,' indicating the operation will not proceed without explicit confirmation. This exceeds what annotations alone provide.

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 sentence with a clear warning and instruction. It is front-loaded with the destructive warning and immediately states the action and the confirmation requirement. No wasted words.

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 mutation tool with full schema coverage, the description plus schema covers the essential information: the operation, the confirmation gate, and the platform default. It does not describe error conditions or post-conditions, but these are not critical for such a straightforward 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?

Schema description coverage is 100%, so the baseline is 3. The description adds no additional parameter meaning; the confirm requirement is already fully documented in the schema. The actionName and triggerName formats are also already described in the 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 clearly states the action: 'Unlink an action from a trigger.' This specific verb+resource phrasing distinguishes it from sibling tools like ncloud_functions_link_trigger_action (the opposite operation) and ncloud_functions_delete_trigger (deletes the entire trigger).

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

Usage Guidelines2/5

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

The description provides no guidance on when to choose this tool over alternatives. It does instruct 'Set confirm=true to execute,' but this is a parameter-related condition rather than tool-selection guidance. There is no mention of when to use unlinking vs linking or deleting.

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