ncloud-gov-mcp-server

ncloud_drm_get_site_logs

Read-only

Get event logs for a DRM site by site ID with pagination options to monitor activities and diagnose issues.

Instructions

Get event logs for a DRM site

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": {
      "siteId": "<siteId>"
    },
    "name": "ncloud_drm_get_site_logs"
  }
}

Input Schema

Name	Required	Description
`pageNo`	No	Page number (1~N, default 1)
`siteId`	Yes	Site ID to query logs for
`pageSize`	No	Items per page (1~100)

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.1Aug 2, 2026

TDQS

A3.5/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true, covering the safety profile. The description adds that it retrieves 'event logs', which clarifies the data type but does not disclose additional behaviors such as ordering, time range, or pagination behavior. Since the read-only nature is annotated, the description does enough for a simple read operation.

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, front-loaded sentence with no unnecessary words or repetition. It efficiently conveys the tool's purpose.

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 simple read-only log retrieval with full schema coverage and readOnlyHint annotation, the description is minimally adequate. However, it lacks any broader context such as whether logs are recent, how they are sorted, or when this tool should be preferred. Without an output schema, it would benefit from a brief note on return format or filter behavior.

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%, so all three parameters (siteId, pageNo, pageSize) already have descriptions in the schema. The description does not add extra meaning beyond resourcing, but the schema fully documents the parameters. Baseline 3 is appropriate.

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') and the resource ('event logs for a DRM site'). It is specific enough to distinguish from sibling tools like ncloud_drm_get_policy_logs (policy logs vs event logs) and generic search_logs. The verb and resource are unambiguous.

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. It does not mention related tools like ncloud_drm_get_policy_logs or ncloud_search_logs, nor does it state any exclusions or prerequisites. The description is purely functional with no contextual usage direction.

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

Deploy Server