Skip to main content
Glama
sjk4425

ncloud-mcp-server

by sjk4425
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

ncloud_functions_invoke_action

Invoke a Cloud Functions action synchronously to get its result (activation ID, duration, response). If the action exceeds the timeout, it returns only the activation ID for later retrieval via activation details.

Instructions

Invoke an action synchronously and return its result (activationId, duration, response.result). If the action runs longer than timeout, only the activationId is returned — fetch the outcome later with ncloud_functions_get_action_activation_detail. web/sequence-web actions cannot handle raw HTTP here; use an API Gateway trigger for that.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
paramsNoRuntime parameters passed to the action (highest precedence)
timeoutNoMax time to wait for the response in ms (0-60000, default 60000)
platformNoPlatform (default: vpc). Singapore/Japan regions support vpc only.vpc
actionNameYesName of the action to invoke
packageNameNoPackage name ('-' = unpackaged action)-

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed7 schema fields changedv1.15.0
    • addedInput schema / properties / packageName / default
      Added value: +"-"
    • changedInput schema / properties / packageName / description
      Previous value: -"Package name containing the action"New value: +"Package name ('-' = unpackaged action)"
    • changedInput schema / properties / params / description
      Previous value: -"Runtime parameters to pass to the action"New value: +"Runtime parameters passed to the action (highest precedence)"
    • changedInput schema / properties / platform / description
      Previous value: -"Platform type (default: vpc)"New value: +"Platform (default: vpc). Singapore/Japan regions support vpc only."
    • changedInput schema / properties / timeout / description
      Previous value: -"Invocation timeout in milliseconds (0~60000, default: 60000)"New value: +"Max time to wait for the response in ms (0-60000, default 60000)"
    • changedInput schema / properties / timeout / type
      Previous value: -"number"New value: +"integer"
    • changedInput schema / required
      Previous value: -[
-  "packageName",
-  "actionName"
-]New value: +[
+  "actionName"
+]
  2. First observedv1.10.1

TDQS

A4.4/5.0
Behavior4/5

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

Annotations are empty, so the description carries the full behavioral burden and discharges it well: it discloses partial-return behavior on timeout, the follow-up retrieval path, and the web/sequence-web HTTP limitation. It stops short of noting that invoking an action may trigger side effects or mention auth/cost implications, which is why it isn't a 5.

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?

Three sentences with no filler; the core purpose and return fields are front-loaded, followed by the two most decision-relevant caveats. Every sentence earns its place.

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?

With no output schema and empty annotations, the description covers the essential operational knowledge: what is returned, the timeout edge case, and when to route elsewhere. It does not enumerate the full response structure or side-effect expectations, but for an invocation tool the key decisions an agent must make are covered.

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 detailed descriptions already provided (defaults, range, enum, precedence note for params). The description adds one behavioral consequence tied to timeout (only activationId returned when exceeded), which is useful but marginal relative to the schema's complete coverage.

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?

States a specific verb and resource ('Invoke an action') with the synchronous mode and the three return fields (activationId, duration, response.result). The synchronous qualifier and web/sequence-web limitation distinguish it from related siblings like ncloud_functions_get_action_activation_detail and ncloud_functions_invoke_trigger.

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

Usage Guidelines5/5

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

Gives an explicit when-to-use rule for timeout overflow — 'If the action runs longer than timeout, only the activationId is returned' — and names the alternative tool to fetch the outcome. The web/sequence-web exclusion with API Gateway as the alternative provides clear when-not-to-use guidance.

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