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

ncloud-mcp-server

by sjk4425
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

ncloud_advisor_download_category_results

Read-only

Download an Excel report of Naver Cloud Advisor check results for all items in a SECURITY or COST category, saving to a local path or returning base64 content.

Instructions

Download the Excel report of check results for all items in a category. Saves to savePath or returns base64 content.

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": {
      "categoryCode": "<categoryCode>"
    },
    "name": "ncloud_advisor_download_category_results"
  }
}

Input Schema

NameRequiredDescriptionDefault
savePathNoLocal file path to save the .xlsx to (recommended). If omitted, the file is returned inline as base64 when it is 256 KB or smaller.
categoryCodeYesCheck category code: SECURITY or COST

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv2.0.1
    • addedInput schema / properties / savePath
      Added value: +{
+  "description": "Local file path to save the .xlsx to (recommended). If omitted, the file is returned inline as base64 when it is 256 KB or smaller.",
+  "type": "string"
+}
  2. First observedv1.10.1

TDQS

A3.8/5.0
Behavior4/5

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

With readOnlyHint already covering the safety profile, the description adds real behavioral detail: the output is an Excel file and it either writes to savePath or is returned inline as base64. This reveals the dual output mode beyond what annotations state.

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 compact sentences with the primary purpose front-loaded and the output behavior second; no wasted words.

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 read-only download tool with no output schema, the description tells the agent what is produced (Excel report) and how it is delivered (savePath or base64), which is enough to call it correctly. Only the relationship to sibling download/summary tools is left implicit.

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 both parameters (including the SECURITY/COST enum and the 256 KB inline constraint) are already fully documented in the schema. The description's mention of savePath and base64 merely restates this, adding no syntax or format detail beyond the schema.

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?

States a specific verb ('Download'), the artifact ('Excel report of check results'), and the scope ('all items in a category'). The category scope implicitly distinguishes it from the sibling item-level and all-level download tools, though it does not name them explicitly.

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 only implied by the scope phrase 'for all items in a category'; there is no explicit when-to-use guidance or reference to the sibling tools (download_item_results, download_all_results, get_category_result_summary) that an agent would need to choose between.

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