Skip to main content
Glama
sjk4425

ncloud-mcp-server

by sjk4425
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

ncloud_advisor_download_all_results

Read-only

Download the complete Excel report of all check results in every category. Save it to a local path or receive it as base64 when small.

Instructions

Download the complete Excel report of check results for all categories. Saves to savePath or returns base64 content.

Input Schema

TableJSON 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.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv2.0.1
    • addedInput schema / additionalProperties
      Added value: +false
    • 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.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, so the safety profile is covered. The description adds that the output is an Excel (.xlsx) report and that it either saves to disk or returns base64, but the dual-output behavior and the 256 KB inline cutoff are already spelled out in the schema, so incremental value is modest.

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?

Two short, front-loaded sentences with no filler: the action and scope come first, the output behavior second. Nothing is wasted, though it is minimal rather than richly structured.

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 with one fully documented parameter and a readOnlyHint annotation, the definition covers what the tool returns (an Excel report of all categories) and how the output is delivered. No output schema exists, but the file nature of the result is stated, so little is missing.

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% for the single savePath parameter, and the description merely restates its save-vs-inline behavior without the size threshold the schema provides. Baseline 3 is appropriate when the schema does the documentation work.

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 and resource ('Download the complete Excel report of check results') plus the scope qualifier 'for all categories', which implicitly separates it from ncloud_advisor_download_category_results and ncloud_advisor_download_item_results. It stops short of naming those siblings, so the differentiation is left to inference.

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 phrase 'for all categories' implies when this tool is appropriate versus the category- or item-scoped download siblings, but no explicit when-to-use or alternative routing is given. Adequate but leaves the agent to infer the boundary.

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