Skip to main content
Glama
sjk4425

ncloud-mcp-server

by sjk4425
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

ncloud_functions_link_trigger_action

Link a Cloud Functions action to a trigger so trigger events automatically invoke it. Avoid duplicate rule errors when linking.

Instructions

Link an action to a trigger so the trigger's events invoke it (POST /ncf/api/v2/triggers/{name}/link-action). Fails with 80901 DUPLICATED_RULE if already linked, 80324/80519 when a link limit is exceeded.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
platformNoPlatform (default: vpc). Singapore/Japan regions support vpc only.vpc
actionNameYesAction name. '{packageName}/{actionName}' is also accepted and split automatically.
packageNameNoPackage of the action (default '-' = unpackaged)
triggerNameYesName of the trigger

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv1.15.0
    • changedInput schema / properties / actionName / description
      Previous value: -"Action name in \"{packageName}/{actionName}\" format"New value: +"Action name. '{packageName}/{actionName}' is also accepted and split automatically."
    • addedInput schema / properties / packageName
      Added value: +{
+  "description": "Package of the action (default '-' = unpackaged)",
+  "type": "string"
+}
    • changedInput schema / properties / platform / description
      Previous value: -"Platform type (default: vpc)"New value: +"Platform (default: vpc). Singapore/Japan regions support vpc only."
  2. First observedv1.10.1

TDQS

A3.9/5.0
Behavior3/5

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

Annotations are empty, so the description carries the transparency burden. It usefully discloses failure modes (80901 DUPLICATED_RULE if already linked, 80324/80519 on link limit exceeded) and the consequence of the link. However, it does not mention authorization requirements, reversibility, or any success response, leaving the behavioral picture incomplete for a mutating operation.

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 sentences with no filler. The core purpose is front-loaded, and the error-code details earn their place by helping an agent anticipate common failures. Nothing extraneous is included.

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 mutating tool with no annotations and no output schema, the description is adequate but not fully complete. It explains the action, endpoint, and error conditions, and the schema covers all parameters. Still missing are success-return expectations, prerequisite conditions, and any mention of the complementary unlink 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 applies. The description does not add parameter-level meaning beyond the schema; triggerName, actionName, packageName, and platform are already well documented in the input 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 opens with a specific verb and resource: 'Link an action to a trigger so the trigger's events invoke it.' The endpoint path (POST /ncf/api/v2/triggers/{name}/link-action) further pins down the exact operation, and the verb 'link' clearly distinguishes it from the sibling unlink_trigger_action.

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 conveys the intended use case: when you want a trigger's events to invoke an action. It does not explicitly name alternative tools or state when not to use it, but the linking purpose is clear enough that an agent can decide when this is the right operation.

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