Skip to main content
Glama
aspose-cells-cloud

Aspose.Cells Cloud MCP Server

Official
by aspose-cells-cloud
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Download File

download_file

Retrieve a file from Aspose.Cells Cloud by its unique ID and get its contents as a Base64 string for use in spreadsheet workflows.

Instructions

Download the file identified by the given file_uuid and return its contents as a Base64-encoded string.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
file_uuidYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv26.4.1
    • removedInput schema / properties / file_token
      Removed value: -{
-  "type": "string"
-}
    • addedInput schema / properties / file_uuid
      Added value: +{
+  "type": "string"
+}
    • changedInput schema / required
      Previous value: -[
-  "file_token"
-]New value: +[
+  "file_uuid"
+]
  2. First observedv26.4.0

TDQS

A4/5.0
Behavior3/5

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

No annotations are provided, so the description carries full weight. It discloses the key behavior of returning contents as Base64, but it does not mention error handling, size limits, or whether the operation is purely non-destructive aside from what 'download' implies.

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, front-loaded sentence with no filler or redundant phrasing. Every word earns its place, and the core action and output format are presented immediately.

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 one-parameter tool with no output schema, the description provides the essential information: the input identifies the file and the output is Base64. It is mostly complete, though a mention of error cases or how to obtain file_uuid would strengthen it.

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 description confirms that file_uuid identifies the file to download, which adds a small amount of meaning to the raw schema. However, it does not explain how to obtain a valid UUID, expected format, or any constraints, so it only partially compensates for the 0% schema description coverage.

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?

The description states a specific verb ('Download'), a specific resource ('the file identified by file_uuid'), and the exact result format ('Base64-encoded string'). This clearly distinguishes the tool from siblings like upload_file and the structure/conversion tools.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The intended use is clear: call this when you have a file_uuid and need the file's raw contents returned. It does not explicitly name alternatives or exclusions, but the context is unambiguous for such a simple retrieval tool.

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