Skip to main content
Glama
sjk4425

ncloud-mcp-server

by sjk4425
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

ncloud_get_dashboard_widget_image

Read-only

Download a Cloud Insight dashboard widget image for a time range. Returns its type and size, plus base64 data when small, or writes the image to savePath.

Instructions

Download a dashboard widget image (binary) from Cloud Insight. Returns content type and size, plus base64 data when small; pass savePath to write the image to a file instead.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
endTimeYesEnd time in Unix epoch milliseconds
savePathNoLocal file path to save the image to; when given, the image bytes are not returned inline
widgetIdYesWidget ID (see ncloud_get_dashboard_widgets)
startTimeYesStart time in Unix epoch milliseconds
dashboardIdYesDashboard ID
widgetResolutionModeNoResolution: AUTO (same as dashboard, default) or HIGH (finer)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changedv2.0.1
    • addedInput schema / properties / endTime
      Added value: +{
+  "description": "End time in Unix epoch milliseconds",
+  "type": "number"
+}
    • addedInput schema / properties / savePath
      Added value: +{
+  "description": "Local file path to save the image to; when given, the image bytes are not returned inline",
+  "type": "string"
+}
    • addedInput schema / properties / startTime
      Added value: +{
+  "description": "Start time in Unix epoch milliseconds",
+  "type": "number"
+}
    • changedInput schema / properties / widgetId / description
      Previous value: -"Widget ID to get image for"New value: +"Widget ID (see ncloud_get_dashboard_widgets)"
    • addedInput schema / properties / widgetResolutionMode
      Added value: +{
+  "description": "Resolution: AUTO (same as dashboard, default) or HIGH (finer)",
+  "enum": [
+    "AUTO",
+    "HIGH"
+  ],
+  "type": "string"
+}
    • changedInput schema / required
      Previous value: -[
-  "dashboardId",
-  "widgetId"
-]New value: +[
+  "dashboardId",
+  "widgetId",
+  "startTime",
+  "endTime"
+]
  2. First observedv1.10.1

TDQS

A4/5.0
Behavior4/5

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

Annotations only declare readOnlyHint=true, so the description adds meaningful behavior: it discloses the return payload (content type and size), a conditional output shape (base64 only when small), and an alternate delivery mode (savePath writes to disk instead of inlining). The size threshold 'when small' is left vague, keeping it below a 5.

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?

Two tightly written sentences, front-loaded with the core action and followed by the return/delivery behavior. No filler or redundancy.

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?

With no output schema, the description does the work of explaining what comes back (content type, size, base64) and how savePath changes the response, which is sufficient for a read-only download tool. The exact 'small' cutoff for base64 versus file output is the only notable gap.

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 coverage is 100%, so all six parameters are already documented in the schema. The description restates savePath semantics and hints at output-size-dependent behavior but adds no syntax or format detail beyond what the schema provides, so the baseline 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?

States a specific verb ('Download') and resource ('dashboard widget image') with the source service (Cloud Insight), and the binary-image nature clearly separates it from listing siblings like ncloud_get_dashboard_widgets or ncloud_list_dashboards.

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?

Usage is implied by the task description but the description never states when to use this versus ncloud_query_widget_preview or the widget-listing tool, nor any prerequisites. The savePath note guides invocation mechanics rather than tool selection.

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