Skip to main content
Glama
sjk4425

ncloud-mcp-server

by sjk4425
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

ncloud_cdss_get_os_monitoring

Read-only

Retrieve OS-level metrics for a CDSS cluster node, covering CPU, memory, and disk usage to monitor system performance over a specified time range.

Instructions

Get OS-level monitoring metrics (CPU, memory, disk) for a CDSS cluster 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. 1745280000000) — NOT an ISO 8601 string
computeInstanceNoYesNode instance number (from ncloud_cdss_list_nodes)
serviceGroupInstanceNoYesCluster instance number (path segment)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed9 schema fields changedv1.15.0
    • addedInput schema / properties / computeInstanceNo
      Added value: +{
+  "description": "Node instance number (from ncloud_cdss_list_nodes)",
+  "type": "string"
+}
    • removedInput schema / properties / endTime
      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 / startTime
      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. 1745280000000) — NOT an ISO 8601 string",
+  "type": "number"
+}
    • changedInput schema / required
      Previous value: -[
-  "serviceGroupInstanceNo"
-]New value: +[
+  "serviceGroupInstanceNo",
+  "timeStart",
+  "timeEnd",
+  "metric",
+  "computeInstanceNo"
+]
  2. First observedv1.10.1

TDQS

A3.5/5.0
Behavior3/5

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

The annotations declare readOnlyHint=true, and the description's 'Get' wording aligns with that read-only behavior. The description adds no further behavioral context such as side effects, rate limits, or auth requirements, but with the read-only annotation present the safety profile is adequately covered.

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 filler or repetition. It conveys the essential purpose and metric scope as efficiently as possible.

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

Completeness4/5

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

The schema provides thorough parameter documentation, and the read-only annotation covers side-effect safety. The description contributes the high-level return scope (CPU/memory/disk). With no output schema, a fully explicit response structure would be helpful, but an agent has enough information to invoke the tool correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema already covers all parameters with detailed descriptions (100% coverage), including epoch milliseconds, interval examples, and the single valid metric enum. The description adds meaning by specifying that the returned OS metrics are CPU, memory, and disk, which clarifies what OS_ALL_METRICS actually provides.

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 identifies the operation ('Get'), the resource ('OS-level monitoring metrics'), and the specific metric categories ('CPU, memory, disk') for a 'CDSS cluster node'. It is more specific than the bare tool name and helps separate it from the generic ncloud_cdss_get_monitoring sibling, though it does not explicitly name that alternative.

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?

The description implies usage when OS-level CPU/memory/disk metrics are needed, but it gives no explicit guidance on when to choose this tool over related siblings like ncloud_cdss_get_monitoring. There are no exclusions, prerequisites, or alternative-selection criteria.

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