ncloud-gov-mcp-server

ncloud_cdnplus_get_monitoring

Read-only

Retrieve CDN+ traffic and request monitoring data for specified instances over a custom time range, with optional region filter.

Instructions

Get CDN+ monitoring data (traffic, requests) for one or more instances over a time range

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": {
      "cdnInstanceNoList": "<cdnInstanceNoList>",
      "startDate": "<startDate>",
      "endDate": "<endDate>"
    },
    "name": "ncloud_cdnplus_get_monitoring"
  }
}

Input Schema

Name	Required	Description
`endDate`	Yes	Query end datetime (format: yyyyMMddHHmm)
`regionNo`	No	Region number (defaults to KR region if omitted)
`startDate`	Yes	Query start datetime (format: yyyyMMddHHmm)
`cdnInstanceNoList`	Yes	List of CDN+ instance numbers to query

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?

The readOnlyHint annotation already declares this is a safe read operation. The description adds context about the type of data (traffic, requests) and the multi-instance, time-range scope, but it does not disclose return format, pagination, or other behavioral traits beyond the annotation. This is useful but not rich context, consistent with a 3.

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, well-structured sentence that front-loads the action and resource, with no filler or repetition. Every phrase adds meaning.

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?

There is no output schema, so the description bears responsibility for explaining what the response will contain. It mentions traffic and requests, but it does not describe the response structure, aggregation level, or per-instance behavior. This is a clear gap, making the description minimally viable but incomplete for an agent needing to understand the full result.

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 the baseline is 3. The description reinforces that cdnInstanceNoList is for one or more instances and startDate/endDate form a time range, but it adds no new parameter details beyond what the schema already documents.

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 operation ('Get CDN+ monitoring data') with specific details about what is retrieved (traffic, requests) and the scope (one or more instances over a time range). It is specific enough to distinguish from most sibling tools, though it does not explicitly differentiate from the similar ncloud_globalcdn_get_monitoring tool.

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?

The description implies usage context: it is for retrieving CDN+ monitoring data over a time range for specified instances. However, there is no explicit guidance on when to use this tool versus alternatives (e.g., Global CDN monitoring) or any exclusions, so the guidance is mostly implied.

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

Deploy Server