Skip to main content
Glama
sjk4425

ncloud-mcp-server

by sjk4425
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

ncloud_functions_get_action_activations

Read-only

Retrieve execution history for a Cloud Functions action, including activation IDs, durations, statuses, and total count over the past month.

Instructions

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

Input Schema

TableJSON 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. 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"
+]
  2. First observedv1.10.1

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, so the read-only nature is covered. The description adds value by specifying the return fields (activationId, duration, status, totalCount) and the one-month query window, which are not in the annotations. There is no contradiction.

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?

A single sentence that front-loads the verb and resource, then packs in the time window and output fields. There is no filler or redundant content.

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?

The schema fully documents required parameters, time window semantics, pagination, and platform defaults, and the description covers scope and return fields. The main gap is that it does not explicitly differentiate from the similarly named ncloud_functions_get_activations, which could cause selection ambiguity.

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%, and each parameter (start, end, pageNo, pageSize, platform, actionName, packageName) is already documented in the schema. The description adds no parameter-specific meaning beyond what the schema provides.

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 'List' and identifies the exact resource: 'an action's activations (executions)' with a time window and returned fields. This clearly distinguishes it from sibling detail tools like ncloud_functions_get_action_activation_detail and the more generic ncloud_functions_get_activations.

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 its use case: listing an action's activations from the last month. However, it does not explicitly mention alternatives such as ncloud_functions_get_activations or ncloud_functions_get_action_activation_detail, nor state when to prefer them. No exclusion criteria are provided.

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