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

ncloud-mcp-server

by sjk4425
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

ncloud_functions_get_action_activations

Read-only

List an action's executions from the last month, showing activation ID, duration, status, and total count.

Instructions

List an action's activations (executions) from the last month: activationId, duration, status, plus totalCount

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": {
      "actionName": "<actionName>"
    },
    "name": "ncloud_functions_get_action_activations"
  }
}

Input Schema

NameRequiredDescriptionDefault
endNoEnd of the window as a Unix timestamp in MILLISECONDS (default: now).
startNoStart of the window as a Unix timestamp in MILLISECONDS (default: one month before now). Only the last month is queryable.
pageNoNoPage number (default 1)
pageSizeNoPage size (default 20)
platformNoPlatform (default: vpc). Singapore/Japan regions support vpc only.vpc
actionNameYesName of the action
packageNameNoPackage name ('-' = unpackaged action)-

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv2.0.1
    • changedInput schema / properties / end / description
      Previous value: -"End of the window as a Unix timestamp in MILLISECONDS (default: now)"New value: +"End of the window as a Unix timestamp in MILLISECONDS (default: now)."
  2. Changed14 schema fields changedv1.15.0
    • changedInput schema / properties / end / description
      Previous value: -"End time filter (format: yyyy-MM-ddTHH:mm:ss)"New value: +"End of the window as a Unix timestamp in MILLISECONDS (default: now)"
    • changedInput schema / properties / end / type
      Previous value: -"string"New value: +"integer"
    • 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 / pageNo / description
      Previous value: -"Page number for pagination"New value: +"Page number (default 1)"
    • addedInput schema / properties / pageNo / minimum
      Added value: +1
    • changedInput schema / properties / pageNo / type
      Previous value: -"number"New value: +"integer"
    • changedInput schema / properties / pageSize / description
      Previous value: -"Page size for pagination"New value: +"Page size (default 20)"
    • addedInput schema / properties / pageSize / minimum
      Added value: +1
    • changedInput schema / properties / pageSize / type
      Previous value: -"number"New value: +"integer"
    • 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 / start / description
      Previous value: -"Start time filter (format: yyyy-MM-ddTHH:mm:ss)"New value: +"Start of the window as a Unix timestamp in MILLISECONDS (default: one month before now). Only the last month is queryable."
    • changedInput schema / properties / start / type
      Previous value: -"string"New value: +"integer"
    • changedInput schema / required
      Previous value: -[
-  "packageName",
-  "actionName"
-]New value: +[
+  "actionName"
+]
  3. First observedv1.10.1

TDQS

B3.2/5.0
Behavior3/5

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

readOnlyHint=true already declares the safe read profile, so the bar is lower. The description adds the returned field list (activationId, duration, status, totalCount), which is genuinely useful given no output schema, but the 'last month' constraint merely restates the schema's start/end defaults and pagination behavior is not mentioned.

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?

A single, efficiently constructed sentence with the verb and scope front-loaded and no filler. The trailing field list is somewhat list-like but earns its place by summarizing the return payload.

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 read-only list tool with annotations covering safety and 100% schema coverage, the description is sufficient: it names the resource, the window, and the returned fields. There is no output schema to require more, though it could have flagged pagination.

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 all seven parameters are fully documented in the schema. The description adds no parameter-level detail (e.g. how start/end interact with the one-month cap), so the baseline of 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb ('List') and resource ('an action's activations'), and clarifies the terminology with '(executions)'. It specifies the scope ('from the last month'), which is precise, but does not differentiate itself from close siblings like ncloud_functions_get_activations or ncloud_functions_get_trigger_activations.

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?

The description gives no explicit when-to-use guidance and names no alternatives, despite several sibling tools covering activations (get_activations, get_trigger_activations, get_action_activation_detail). An agent must infer from the name that this is the per-action variant.

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