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

ncloud-gov-mcp-server

by sjk4425
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

ncloud_functions_link_trigger_action

Link a Cloud Functions action to a trigger, enabling automatic execution when the trigger event fires. Specify the trigger name and the action in {package}/{action} format.

Instructions

Link an action to a trigger for event-based execution

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_link_trigger_action"
  }
}

Input Schema

NameRequiredDescriptionDefault
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.5/5.0
Behavior2/5

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

Annotations are empty, so the description carries full responsibility for behavioral disclosure. It states the core action and purpose but does not mention side effects (e.g., whether an existing link is replaced), prerequisites (e.g., trigger and action must exist), or idempotency. This is a meaningful gap for a mutation 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 a single, tightly written sentence with the verb and resource front-loaded. There is no redundate text, making it highly concise and easy to scan.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple 3-parameter mutation with a complete schema and no output schema, this description is minimally adequate. It identifies the operation but lacks contextual details like prerequisites, idempotency, or error conditions. The agent can still invoke it correctly given the schema, but the description doesn't go beyond the bare minimum.

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%: all three parameters have meaningful descriptions in the schema (e.g., actionName format, platform enum). The tool description itself adds no parameter-specific details, so the baseline of 3 for full schema coverage is appropriate.

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 uses a specific verb 'Link' with a clear resource ('an action to a trigger') and adds purpose ('for event-based execution'). This clearly distinguishes it from sibling tools like ncloud_functions_unlink_trigger_action, which removes the link.

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 description implies when to use it (when you want event-driven execution by linking a trigger to an action) but doesn't explicitly state when not to use it or reference alternatives. The sibling unlink tool exists, yet the description doesn't mention it or any exclusions.

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