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

ncloud-gov-mcp-server

by sjk4425
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

ncloud_query_monitoring_data_multiple

Read-only

Query multiple Cloud Insight metrics in a single request to retrieve time-series monitoring data for specified products, metric groups, and dimensions within a time range.

Instructions

Query multiple time-series monitoring data from Cloud Insight in a single request. Supports querying multiple metrics at once.

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": {
      "metrics": "<metrics>",
      "timeStart": "<timeStart>",
      "timeEnd": "<timeEnd>"
    },
    "name": "ncloud_query_monitoring_data_multiple"
  }
}

Input Schema

NameRequiredDescriptionDefault
metricsYesArray of metric queries to execute
timeEndYesEnd time in Unix epoch milliseconds
intervalNoAggregation interval (default: Min5)
timeStartYesStart time in Unix epoch milliseconds
aggregationNoAggregation type (default: AVG)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

B3.4/5.0
Behavior3/5

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

The readOnlyHint=true annotation already declares this as a safe read operation. The description adds the scope of 'single request' and 'multiple metrics' but does not disclose other behavioral traits such as response format, pagination, or limits on the number of metrics, which could be relevant for a monitoring query tool.

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 two sentences with the main point front-loaded. However, the second sentence ('Supports querying multiple metrics at once') largely repeats the key point from the first sentence, creating slight redundancy.

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?

The tool has moderate complexity (5 params, no output schema). The description adequately conveys the core function but does not explain the return value structure, constraints on the metrics array, or how the interval/aggregation defaults affect behavior, leaving room for improvement.

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%, with all five parameters (metrics, timeStart, timeEnd, interval, aggregation) documented in the schema. The description does not add any extra parameter-level meaning beyond what is already in the schema, so the baseline score of 3 is appropriate.

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 uses a specific verb ('Query') and resource ('multiple time-series monitoring data from Cloud Insight'), and emphasizes 'multiple metrics at once' which distinguishes it from singular query tools like ncloud_query_monitoring_data. However, it does not explicitly name the alternative, so it stops short of a perfect score.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies this tool is for querying multiple metrics in a single request, which is useful context. However, it does not explicitly state when to use this tool versus alternatives (e.g., ncloud_query_monitoring_data for single metrics) or provide any exclusion 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