ncloud-gov-mcp-server

ncloud_drm_get_policy_logs

Read-only

Retrieve event logs for a specific DRM policy to monitor security events. Supports pagination and time-based filtering for audit and troubleshooting.

Instructions

Get event logs for a DRM policy

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": {
      "policyId": "<policyId>"
    },
    "name": "ncloud_drm_get_policy_logs"
  }
}

Input Schema

Name	Required	Description
`pageNo`	No	Page number (1~N, default 1)
`endTime`	No	Query end time (Unix epoch milliseconds)
`pageSize`	No	Items per page (1~100)
`policyId`	Yes	DRM policy ID to query logs for
`startTime`	No	Query start time (Unix epoch milliseconds)

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.1Aug 2, 2026

TDQS

B3.1/5.0

Behavior2/5

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

The readOnlyHint=true annotation aligns with the 'Get' operation, but the description adds no additional behavioral context such as pagination behavior, time range handling, or event log format. It merely restates the operation, providing no value beyond the annotation.

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 concise sentence with no redundant words. It is appropriately sized for a straightforward query operation.

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?

With no output schema and a minimal description, the tool lacks context about return format, pagination limits, or event types. The schema covers query parameters, but for a log retrieval tool this is a meaningful gap that could confuse agents needing to interpret results.

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?

The input schema has 100% coverage with descriptions for all five parameters, so the schema handles semantic meaning. The tool description itself adds no parameter-specific information, but this is acceptable given the schema's completeness.

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?

The description clearly states the action ('Get') and the resource ('event logs for a DRM policy'), making it specific and distinct from sibling tools like ncloud_drm_get_site_logs. However, it does not explicitly name alternatives or contrast itself, so it falls short of full sibling differentiation.

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 other log-related tools such as ncloud_drm_get_site_logs or ncloud_search_logs. The description is a bare statement of functionality with no context about use cases or exclusions.

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

Deploy Server