ncloud-gov-mcp-server

ncloud_search_event_count

Read-only

Count monitoring events from Cloud Insight within a specified time range, with optional filters for product, severity, and rule group.

Instructions

Get the count of monitoring events from Cloud Insight within a specified 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": {
      "startTime": "<startTime>",
      "endTime": "<endTime>"
    },
    "name": "ncloud_search_event_count"
  }
}

Input Schema

Name	Required	Description
`endTime`	Yes	End time in Unix epoch milliseconds
`prodKey`	No	Product key to filter events
`startTime`	Yes	Start time in Unix epoch milliseconds
`eventLevel`	No	Event severity level filter
`ruleGroupId`	No	Rule group ID to filter events

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 description adds no behavioral context beyond the readOnlyHint annotation. It does not disclose return format, pagination, potential performance costs, or any rate-limiting constraints. It is consistent with the annotation but contributes no extra transparency.

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 succinct sentence, front-loaded with the action and object, with no filler or redundant phrases.

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 count tool with full schema coverage and a readOnly annotation, the description is minimally adequate. However, it does not specify the return value (e.g., just the integer count) nor differentiate from the related event search tools, leaving some contextual gaps.

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 parameters are already well-documented. The description only reinforces the time-range aspect and does not add new semantic meaning beyond the schema, meriting the baseline score.

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 verb ('Get the count') and resource ('monitoring events from Cloud Insight') with an explicit time-range scope. It does not explicitly contrast with sibling tools like ncloud_search_events, but the count-vs-list distinction is inferable from the name.

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 given on when to use this tool versus alternatives. It does not mention that ncloud_search_events returns actual events while this returns only a count, nor any prerequisites or context for choosing this count endpoint.

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

Deploy Server