Skip to main content
Glama
Sign In
ncloud-mcp-server

ncloud-mcp-server

by sjk4425
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

ncloud_search_event_by_id

Read-only

Retrieve detailed monitoring event information by event ID and rule ID within a specified time range to identify and inspect a specific event.

Instructions

Get detailed information about a specific monitoring event by event ID and rule ID.

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": {
      "eventId": "<eventId>",
      "ruleId": "<ruleId>",
      "startTime": "<startTime>",
      "endTime": "<endTime>"
    },
    "name": "ncloud_search_event_by_id"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryNoSearch by rule name, metric name or resource name
ruleIdYesEvent Rule ID associated with the event
endTimeYesEnd time in Unix epoch milliseconds
eventIdYesEvent ID to retrieve details for
pageNumNoPage number (default: 1)
pageSizeNoNumber of results per page (default: 20)
startTimeYesStart time in Unix epoch milliseconds
onlyFetchUnCloseEventNoOnly return events that are not closed yet (default: false)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed8 schema fields changedv2.0.1
    • addedInput schema / properties / endTime
      Added value: +{
+  "description": "End time in Unix epoch milliseconds",
+  "type": "number"
+}
    • addedInput schema / properties / onlyFetchUnCloseEvent
      Added value: +{
+  "description": "Only return events that are not closed yet (default: false)",
+  "type": "boolean"
+}
    • addedInput schema / properties / pageNum
      Added value: +{
+  "description": "Page number (default: 1)",
+  "type": "number"
+}
    • addedInput schema / properties / pageSize
      Added value: +{
+  "description": "Number of results per page (default: 20)",
+  "type": "number"
+}
    • addedInput schema / properties / query
      Added value: +{
+  "description": "Search by rule name, metric name or resource name",
+  "type": "string"
+}
    • changedInput schema / properties / ruleId / description
      Previous value: -"Rule ID associated with the event"New value: +"Event Rule ID associated with the event"
    • addedInput schema / properties / startTime
      Added value: +{
+  "description": "Start time in Unix epoch milliseconds",
+  "type": "number"
+}
    • changedInput schema / required
      Previous value: -[
-  "eventId",
-  "ruleId"
-]New value: +[
+  "eventId",
+  "ruleId",
+  "startTime",
+  "endTime"
+]
  2. First observedv1.10.1

TDQS

C2.9/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true, so the safety profile is covered. Beyond that the description discloses nothing: no mention of the mandatory time window, pagination behavior (pageNum/pageSize), or the onlyFetchUnCloseEvent filter that materially changes results.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single tight sentence with the resource and key identifiers front-loaded; no padding. It is efficient, but the brevity comes at the cost of the missing usage and parameter context.

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 an 8-parameter read tool with four required parameters and no output schema, the description leaves the mandatory time-range requirement and pagination semantics to the schema. It is minimally viable but not complete enough to call correctly from the description alone.

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 schema already documents all 8 parameters and the baseline of 3 applies. The description names only eventId and ruleId, omitting the equally required startTime/endTime, so it adds no meaning beyond the schema.

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?

States a specific verb+resource ('Get detailed information about a specific monitoring event') and the key identifiers (event ID, rule ID). It distinguishes itself implicitly from the list-oriented sibling ncloud_search_events by promising detail for a single event, but it never names that sibling or otherwise explicitly boundary itself.

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 when-to-use or when-not-to-use guidance. The presence of ncloud_search_events and ncloud_search_event_count as siblings makes a routing statement ('use this after search_events returns an event ID') genuinely valuable, and it is absent.

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

Deploy Server

Other Tools