ncloud-gov-mcp-server

ncloud_get_dashboard_widget_image

Read-only

Retrieve a widget image from a Cloud Insight dashboard as base64 data. Specify dashboard and widget IDs to download the image.

Instructions

Download a dashboard widget image from Cloud Insight. Returns image data as base64.

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": {
      "dashboardId": "<dashboardId>",
      "widgetId": "<widgetId>"
    },
    "name": "ncloud_get_dashboard_widget_image"
  }
}

Input Schema

Name	Required	Description	Default
`widgetId`	Yes	Widget ID to get image for
`dashboardId`	Yes	Dashboard ID

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.1Aug 2, 2026

TDQS

B3.4/5.0

Behavior3/5

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

Annotations declare readOnlyHint=true, and the description doesn't contradict that. It adds useful context by stating the return format is base64-encoded image data, but it doesn't disclose potential error conditions, image format details, or size limits. With annotations covering the safety profile, this score is appropriate.

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 exceptionally concise with two sentences, front-loading the action and return format. Every word adds value, with no redundancy or irrelevant details.

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?

For a simple read-only fetch with two well-documented parameters, the description adequately covers the essential behavior—downloads an image and returns base64 data. It doesn't explain how to obtain widget IDs, but sibling tools and the schema provide sufficient context, making it complete enough for this 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?

The schema provides 100% description coverage for both parameters (dashboardId and widgetId). The description adds no extra meaning beyond what the schema already includes, so the baseline score of 3 applies.

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 'Download' and identifies the resource as a 'dashboard widget image' from Cloud Insight, clearly stating what the tool does. It does not explicitly differentiate from siblings like ncloud_get_dashboard_widgets or ncloud_query_widget_preview, though the word 'image' provides some implicit distinction.

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?

There is no guidance about when to use this tool versus alternatives. It doesn't mention that other tools list widgets or preview data, or outline any prerequisites or related operations, leaving the agent to infer usage from the name and schema.

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

Deploy Server