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

ncloud-mcp-server

by sjk4425
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

ncloud_functions_get_trigger_activation_detail

Read-only

Retrieve a trigger activation's result, status, success flag, logs, and start time. If the activation is not found right after invocation, wait and retry.

Instructions

Get one trigger activation: result, status, success flag, logs, start time. Right after an invocation the detail can return 80518 TRIGGER_ACTIVATION_NOT_FOUND for ~30-40 s even though the id is already in the activation list (observed live 2026-09-15) — retry after a short wait.

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>",
      "activationId": "<activationId>"
    },
    "name": "ncloud_functions_get_trigger_activation_detail"
  }
}

Input Schema

NameRequiredDescriptionDefault
platformNoPlatform (default: vpc). Singapore/Japan regions support vpc only.vpc
triggerNameYesName of the trigger
activationIdYesActivation ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.15.0
    • changedInput schema / properties / activationId / description
      Previous value: -"Activation ID to retrieve details for"New value: +"Activation ID"
    • 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

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, so the description correctly avoids repeating that. It adds a valuable, concrete behavioral caveat about the 80518 error and the ~30-40s retry window, which is beyond structured fields and helps an agent handle failures correctly.

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, no filler. The first sentence states the core purpose with the returned fields; the second delivers a crucial retry tip. Every word earns its place and the key information is front-loaded.

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?

For a single-detail read with three parameters and no output schema, the description covers the essential behavior: what it returns and the transient error condition. It doesn't describe return format, but given the absence of an output schema and the simple scope, it is adequately complete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so all parameters are documented. The description adds practical context about activationId specifically—that it may transiently return NOT_FOUND—which is parameter-relevant and not in the schema. This enriches parameter understanding beyond the baseline.

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 clearly states the tool gets one trigger activation and lists the exact fields returned (result, status, success flag, logs, start time). This distinguishes it from list tools like ncloud_functions_get_trigger_activations, making the purpose unambiguous.

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 it is for retrieving a single activation detail rather than a list, but it does not explicitly name alternatives or state when to prefer this tool over ncloud_functions_get_trigger_activations or similar siblings. The guidance is implicit rather than 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