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

ncloud-gov-mcp-server

by sjk4425
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

ncloud_functions_create_trigger

Create or update Cloud Functions triggers to automate function invocation based on cron schedules, GitHub events, object storage changes, or source commits across NCP Gov Cloud.

Instructions

Create or update a Cloud Functions trigger

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>",
      "type": "<type>",
      "trigger": "<trigger>"
    },
    "name": "ncloud_functions_create_trigger"
  }
}

Input Schema

NameRequiredDescriptionDefault
linkNoLink configuration for GitHub type: { productId, apiName, stageName }
typeYesTrigger type
triggerYesTrigger configuration object (structure varies by type)
platformNoPlatform type (default: vpc)vpc
triggerNameYesName of the trigger to create or update

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

A3.9/5.0
Behavior4/5

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

Annotations only include destructiveHint:false, so the description adds value by clarifying that the tool can both create and update (an upsert behavior). This goes beyond the tool name and the annotation. However, it does not disclose side effects like overwriting existing trigger configurations or permission requirements, but given the annotation coverage this is a reasonable level of transparency.

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 six-word sentence that is front-loaded with the verb and resource. There is no filler, redundancy, or unnecessary detail.

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?

The tool has moderate complexity with nested objects like 'trigger' whose structure 'varies by type' and an open-ended additionalProperties schema. The description does not explain return values (no output schema) or type-specific configuration requirements. While the schema provides enum values and partial hints, the sparse description leaves notable gaps for correctly constructing configuration objects.

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% with all five parameters having descriptions and two having enums. The tool description adds no additional parameter meaning, so the baseline score of 3 applies per the rubric.

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 'Create or update a Cloud Functions trigger' uses a specific verb and resource, clearly distinguishing it from sibling tools like ncloud_functions_create_action, ncloud_functions_create_package, ncloud_functions_delete_trigger, and ncloud_functions_invoke_trigger. It precisely conveys both creation and update operations.

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 gives no explicit guidance on when to use this tool versus alternatives, such as 'for listing triggers use list_triggers'. Usage is implied by the tool name and sibling context, but there are no stated exclusions or prerequisites. It is adequate but not explicit.

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