Skip to main content
Glama
sjk4425

ncloud-mcp-server

by sjk4425
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

ncloud_ses_get_monitoring

Read-only

Retrieve monitoring metrics for a Search Engine Service cluster or node. Specify cluster instance, time range, and metric set to get search-engine performance data.

Instructions

Get search-engine monitoring data for a Search Engine Service cluster or 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. 1742747874000) — NOT an ISO 8601 string
computeInstanceNoNoNode instance number. Required for node-level metrics
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. Required for node-level metrics",
+  "type": "string"
+}
    • 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)",
+  "type": "string"
+}
    • addedInput schema / properties / metric
      Added value: +{
+  "description": "Metric set to retrieve",
+  "enum": [
+    "CLUSTER_ALL_METRICS",
+    "SES_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. 1742747874000) — NOT an ISO 8601 string",
+  "type": "number"
+}
    • changedInput schema / required
      Previous value: -[
-  "serviceGroupInstanceNo"
-]New value: +[
+  "serviceGroupInstanceNo",
+  "timeStart",
+  "timeEnd",
+  "metric"
+]
  2. First observedv1.10.1

TDQS

B3.4/5.0
Behavior3/5

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

The annotation readOnlyHint=true already signals this is a safe read operation. The description adds the cluster-or-node scoping context, which is useful, but does not disclose return format, pagination, or any constraints beyond that. With annotations covering safety, the added context is modest.

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, front-loaded sentence with no filler. It efficiently states the purpose and scope without redundancy.

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?

For a tool with six parameters, four required, and no output schema, this description is too sparse. It does not explain what 'monitoring data' includes, how to specify node-level vs cluster-level (computeInstanceNo requirement), or what the response might look like. An agent would need to rely entirely on the schema, which lacks usage context.

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 every parameter is documented. The description itself adds no extra semantic meaning beyond what the schema provides, such as relationships between parameters or usage hints. Baseline 3 applies because the schema does the heavy lifting.

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 clearly states the action ('Get') and the specific resource ('search-engine monitoring data for a Search Engine Service cluster or node'). It distinguishes itself from siblings like ncloud_ses_get_os_monitoring (OS monitoring) and ncloud_cdss_get_monitoring (Kafka) by naming the SES service and the cluster/node scope.

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 versus alternatives, nor on choosing cluster-level vs node-level metrics. The description does not mention the required computeInstanceNo for node-level queries or how to select the appropriate metric. An agent would have to infer usage from the schema alone.

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