Skip to main content
Glama
sjk4425

ncloud-mcp-server

by sjk4425
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

ncloud_functions_get_trigger_activations

Read-only

List a trigger's activations from the past month, including activation ID, duration, status, and total count, with optional time range and pagination.

Instructions

List a trigger's activations 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
triggerNameYesName of the trigger

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. Changed11 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"
    • 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"
  3. First observedv1.10.1

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, so the safety profile is covered. Beyond that the description discloses the one-month retention window and enumerates return fields (activationId, duration, status, totalCount), which is real added value. It stops short of describing pagination behavior or what totalCount represents.

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 front-loaded sentence that names the resource, the time scope, and the payload contents with zero filler. Nothing could be removed without losing information.

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, the description compensates by listing the returned fields, and it flags the last-month constraint on data availability. It leaves page/totalCount semantics and pagination traversal unstated, which is a minor gap for a 6-parameter list tool.

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 the schema itself documents every parameter including the millisecond timestamps, the one-month queryability limit, pagination defaults, and the platform enum. The description adds no parameter-level meaning beyond that, 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+resource with scope: listing a trigger's activations over the last month, including the returned fields. It distinguishes itself implicitly from action-scoped or account-wide siblings by naming 'a trigger's activations,' but never names the alternatives explicitly.

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?

Usage is implied by the tool name and the 'last month' scope, but there is no statement of when to use this versus ncloud_functions_get_activations, ncloud_functions_get_action_activations, or ncloud_functions_get_trigger_activation_detail. Nothing is misleading, but the agent must infer routing on its own.

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