Skip to main content
Glama
sjk4425

ncloud-mcp-server

by sjk4425
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

ncloud_cdss_get_monitoring

Read-only

Retrieve Kafka monitoring metrics for a CDSS cluster node by specifying cluster, node, time range, and metric set.

Instructions

Get Kafka monitoring metrics for a CDSS cluster node

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
metricYesMetric set to retrieve
timeEndYesEnd time as epoch milliseconds
intervalNoAggregation interval (e.g. Min1, Min30, Hour2, Day1)
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)",
+  "type": "string"
+}
    • addedInput schema / properties / metric
      Added value: +{
+  "description": "Metric set to retrieve",
+  "enum": [
+    "CLUSTER_ALL_METRICS",
+    "BROKER_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.6/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 read operation, so the description does not need to repeat that. However, the description adds no additional behavioral details such as response format, pagination, or any limitations. It simply states the purpose, which is acceptable but not enriching.

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, direct sentence with no unnecessary words. The core action and object are front-loaded, making it immediately clear what the tool does.

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?

Given the 100% schema coverage and the readOnlyHint annotation, the description covers the essential purpose. It does not describe the return value, but no output schema is present and that may not be critical. The main gap is lack of usage guidance, which is already scored separately. Overall, the description is sufficient for a read-only metric retrieval tool.

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%, meaning all six parameters have explicit descriptions in the schema. The description adds no parameter-specific information beyond what the schema already provides, so the baseline of 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description 'Get Kafka monitoring metrics for a CDSS cluster node' clearly states a specific verb, resource type (Kafka monitoring metrics), and scope (CDSS cluster node), distinguishing it from related tools like ncloud_cdss_get_os_monitoring and ncloud_cdss_get_broker_info without ambiguity.

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 provides no guidance on when to use this tool versus alternatives. It does not mention ncloud_cdss_get_os_monitoring or other monitoring tools, nor any conditions or exclusions. An agent would have to infer from the name and context, which is weak.

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