ncloud-gov-mcp-server

ncloud_query_widget_preview

Read-only

Query Cloud Insight widget preview data by specifying metric, time range, aggregation, and dimension filters for a given product key.

Instructions

Query widget preview data from Cloud Insight by specifying metrics directly.

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": {
      "prodKey": "<prodKey>",
      "metric": "<metric>",
      "timeStart": "<timeStart>",
      "timeEnd": "<timeEnd>"
    },
    "name": "ncloud_query_widget_preview"
  }
}

Input Schema

Name	Required	Description
`metric`	Yes	Metric name to query
`prodKey`	Yes	Product key (cw_key)
`timeEnd`	Yes	End time in Unix epoch milliseconds
`interval`	No	Aggregation interval
`timeStart`	Yes	Start time in Unix epoch milliseconds
`dimensions`	No	Dimension filters as key-value pairs
`aggregation`	No	Aggregation type

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.1Aug 2, 2026

TDQS

B3.2/5.0

Behavior3/5

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

Annotations declare readOnlyHint=true, and the description's 'Query' aligns with a read-only operation. The phrase 'by specifying metrics directly' adds a bit of context about how it works, but the description doesn't disclose response format, pagination, or other behavioral traits. It adds some value but not rich context.

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 sentence of 10 words, front-loaded with the verb 'Query'. It is concise, free of fluff, and gets straight to the point. While more context could be added elsewhere, the structure itself is exemplary.

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 7 parameters, no output schema, and only a terse description, the tool lacks essential surrounding context. The description doesn't explain what 'widget preview data' means, how the output is returned, or when to use this over other query tools. The readOnlyHint and schema cover some gaps, but the description alone is insufficient.

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?

All 7 parameters have schema descriptions, so the schema does the heavy lifting. The description's 'by specifying metrics directly' maps to the 'metric' parameter but adds no new meaning beyond the schema. Baseline 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 clearly states the tool does 'Query widget preview data from Cloud Insight' with the qualifier 'by specifying metrics directly'. It names a specific verb and resource, which is clear, but it doesn't explicitly contrast with sibling tools like ncloud_query_monitoring_data or ncloud_get_dashboard_widgets.

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 exclusions, prerequisites, or related tools, despite the large sibling list containing similar query and dashboard tools. Usage context is entirely absent.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server