Skip to main content
Glama
sjk4425

ncloud-mcp-server

by sjk4425
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

ncloud_kms_get_key_activity_logs

Read-only

Retrieve activity logs and usage history for a specific KMS key to audit access, track changes, and investigate events by key tag and time range.

Instructions

Get activity logs (usage history) for a specific KMS key.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
keyTagYesKey tag - unique identifier derived from key name
pageNoNoPage number (default: 1)
keywordNoKeyword filter
pageSizeNoPage size (default: 100)
timestampToNoEnd of the range (Unix epoch milliseconds)
timestampFromNoStart of the range (Unix epoch milliseconds)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv2.0.1
    • addedInput schema / properties / keyword
      Added value: +{
+  "description": "Keyword filter",
+  "type": "string"
+}
    • addedInput schema / properties / timestampFrom
      Added value: +{
+  "description": "Start of the range (Unix epoch milliseconds)",
+  "type": "number"
+}
    • addedInput schema / properties / timestampTo
      Added value: +{
+  "description": "End of the range (Unix epoch milliseconds)",
+  "type": "number"
+}
  2. First observedv1.10.1

TDQS

B3.3/5.0
Behavior3/5

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

readOnlyHint=true already establishes this is a safe read, so the description's only added value is glossing 'activity logs' as 'usage history'. It does not disclose pagination behavior, result ordering, retention window, or whether the caller needs key-level permissions.

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 with the verb, resource, parenthetical clarification, and scope. No filler or redundancy.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a read-only log-retrieval tool with a fully documented schema this is minimally adequate, but with no output schema the description could reasonably say what an activity-log entry contains or how paging works, which it omits.

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 coverage is 100%, so keyTag, pageNo, keyword, pageSize, timestampFrom, and timestampTo are all already documented in the schema. The description only implies the keyTag requirement via 'for a specific KMS key' and adds nothing about filtering or time-range semantics. Baseline 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 and resource ('Get activity logs ... for a specific KMS key') and clarifies the resource with '(usage history)'. It is clear what the tool returns, but it does not distinguish itself from near siblings such as ncloud_kms_get_latest_use_info, which an agent could confuse it with.

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 when-to-use or when-not-to-use guidance and names no alternative, even though ncloud_kms_get_latest_use_info and the key-list tools exist as plausible candidates. The agent must infer the choice from the tool name alone.

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