Skip to main content
Glama
sjk4425

ncloud-mcp-server

by sjk4425
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

ncloud_ses_get_os_monitoring

Read-only

Retrieve OS-level monitoring metrics for a Search Engine Service node by specifying cluster, instance, time range, and metric set.

Instructions

Get OS-level monitoring data for a Search Engine Service node

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
metricYesMetric set to retrieve. OS_ALL_METRICS is the only valid value
timeEndYesEnd time as epoch milliseconds
intervalNoAggregation interval (e.g. Min1, Min30, Hour2, Day1). Default: Min1
timeStartYesStart time as epoch milliseconds (e.g. 1742520660000) — NOT an ISO 8601 string
computeInstanceNoYesNode instance number
serviceGroupInstanceNoYesCluster instance number (path segment)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed8 schema fields changedv1.15.0
    • removedInput schema / properties / endDateTime
      Removed value: -{
-  "description": "End time (ISO 8601 format)",
-  "type": "string"
-}
    • addedInput schema / properties / interval
      Added value: +{
+  "description": "Aggregation interval (e.g. Min1, Min30, Hour2, Day1). Default: Min1",
+  "type": "string"
+}
    • addedInput schema / properties / metric
      Added value: +{
+  "description": "Metric set to retrieve. OS_ALL_METRICS is the only valid value",
+  "enum": [
+    "OS_ALL_METRICS"
+  ],
+  "type": "string"
+}
    • changedInput schema / properties / serviceGroupInstanceNo / description
      Previous value: -"Cluster instance number"New value: +"Cluster instance number (path segment)"
    • removedInput schema / properties / startDateTime
      Removed value: -{
-  "description": "Start time (ISO 8601 format)",
-  "type": "string"
-}
    • addedInput schema / properties / timeEnd
      Added value: +{
+  "description": "End time as epoch milliseconds",
+  "type": "number"
+}
    • addedInput schema / properties / timeStart
      Added value: +{
+  "description": "Start time as epoch milliseconds (e.g. 1742520660000) — NOT an ISO 8601 string",
+  "type": "number"
+}
    • changedInput schema / required
      Previous value: -[
-  "serviceGroupInstanceNo",
-  "computeInstanceNo"
-]New value: +[
+  "serviceGroupInstanceNo",
+  "computeInstanceNo",
+  "timeStart",
+  "timeEnd",
+  "metric"
+]
  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?

The description only says 'Get' and adds no behavioral context beyond the readOnlyHint annotation. It does not mention response format, aggregation details, time-range limits, rate limits, or any side effects, leaving the agent without additional behavior insights.

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?

The description is a single sentence with no wasted words and is front-loaded with the action and resource. It is appropriately concise, though its brevity omits usage guidance that could have been included without harming clarity.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, the description should at least hint at what the response contains or any special limitations, but it does not. It also fails to clarify how this tool differs from ncloud_ses_get_monitoring, so an agent cannot fully determine when to use it or what data to expect.

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 input schema already documents all six parameters with descriptions. The tool description adds no extra parameter semantics, so the baseline 3 applies.

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 states 'Get OS-level monitoring data for a Search Engine Service node' – a specific verb, resource, and scope. The qualifier 'OS-level' hints at differentiation from generic monitoring tools like ncloud_ses_get_monitoring, but it does not explicitly name an alternative, so there is some sibling differentiation but not explicit.

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 instead of alternatives such as ncloud_ses_get_monitoring or ncloud_cdss_get_os_monitoring. There are no prerequisites, exclusions, or context that would help an agent choose between related monitoring tools.

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