ncloud-gov-mcp-server

ncloud_kms_get_key_activity_logs

Read-only

Retrieve usage history for a KMS key using its unique tag. Paginate results with pageNo and pageSize to manage large activity logs.

Instructions

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

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": {
      "keyTag": "<keyTag>"
    },
    "name": "ncloud_kms_get_key_activity_logs"
  }
}

Input Schema

Name	Required	Description
`keyTag`	Yes	Key tag - unique identifier derived from key name
`pageNo`	No	Page number (default: 1)
`pageSize`	No	Page size (default: 100)

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.1Aug 2, 2026

TDQS

A3.6/5.0

Behavior3/5

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

The annotation readOnlyHint=true already covers the read-only nature. The description adds minimal context with the parenthetical '(usage history)', which clarifies the content of the logs but does not disclose other behavioral traits such as pagination behavior, required permissions, or return format. No contradiction with annotations.

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?

The description is a single, focused sentence that front-loads the verb and object. Every word contributes; there is no redundant or filler 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?

For a simple retrieval tool with a fully described schema and a read-only annotation, the description is adequate. It conveys the core purpose and scope. However, it lacks explicit mention of pagination or prerequisite keyTag, though these are visible in the schema. Overall, it is complete enough for an agent to invoke correctly.

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%; all parameters (keyTag, pageNo, pageSize) have clear descriptions in the schema. The tool description adds no additional parameter semantics beyond what the schema already provides, so the baseline score of 3 applies.

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 action ('Get'), the resource ('activity logs'), and the scope ('for a specific KMS key'). It distinguishes this tool from siblings like ncloud_kms_get_latest_use_info or ncloud_kms_get_key_info by focusing on activity/usage history.

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?

No guidance is provided on when to use this tool versus alternatives. There is no mention of related tools like ncloud_kms_get_latest_use_info or when one might prefer this over other logging tools. The only inferred usage is from the tool name and description.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server