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

ncloud-gov-mcp-server

by sjk4425
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

ncloud_functions_invoke_trigger

Trigger a Cloud Functions execution on demand by providing the trigger name and optional runtime parameters.

Instructions

Manually invoke 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>"
    },
    "name": "ncloud_functions_invoke_trigger"
  }
}

Input Schema

NameRequiredDescriptionDefault
paramsNoRuntime parameters to pass to the trigger
platformNoPlatform type (default: vpc)vpc
triggerNameYesName of the trigger to invoke

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

B3.1/5.0
Behavior2/5

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

Annotations are empty, so the description carries the full burden of behavioral disclosure. It does not mention side effects, permissions, whether the invocation is synchronous/asynchronous, or what results are returned. 'Invoke' implies execution, but no additional behavioral context is provided.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, concise sentence with no unnecessary words. It is appropriately scoped for a simple tool, though it could include more substance without becoming verbose.

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

Completeness2/5

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

Although the schema covers parameters, the overall context is incomplete. There is no usage guidance, no behavioral information about side effects, and no explanation of what happens when a trigger is invoked. For an execution-type tool with no annotations, this is insufficient for an agent to confidently select and use it.

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 schema already documents all three parameters (triggerName, platform, params). The description adds no extra parameter-level semantics, leaving the baseline at 3.

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 ('invoke') and resource ('Cloud Functions trigger'), clearly stating what the tool does. It distinguishes from sibling tools such as ncloud_functions_invoke_action (which invokes an action directly) and read-only trigger tools like ncloud_functions_list_triggers or ncloud_functions_get_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?

No guidance is given about when to use this tool versus alternatives. It does not mention that this is for manually triggering an action, nor does it compare to ncloud_functions_invoke_action or explain scenarios where a manual trigger is appropriate. The description only states the action, leaving the agent without context for selection.

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