Skip to main content
Glama
aspose-cells-cloud

Aspose.Cells Cloud MCP Server

Official
by aspose-cells-cloud
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Save Spreadsheet As With Scaling Mode

save_spreadsheet_as_with_scaling_mode

Convert a stored spreadsheet to another format with print scaling: fit all data on one page or fit columns to page width, preventing truncated page layout in large reports.

Instructions

Save a spreadsheet in cloud storage to another format while enforcing a print-scaling strategy for large reports (e.g. compress all data onto one page, or fit columns to page width) so the output matches the intended page layout instead of truncating content. Scaling only applies when the target format's save options support it; otherwise the call fails with a clear error rather than silently ignoring the mode.

Parameters:

  • file_uuid: The unique identifier of the stored workbook.

  • target_format: The desired output format (e.g. 'PDF', 'CSV', 'XLSX').

  • scaling_mode: one of NoScaling, FitSheetOnOnePage, FitAllColumnsOnOnePage.

    • NoScaling: no automatic scaling; honors the worksheet's own page setup.

    • FitSheetOnOnePage: scale all rows and columns onto a single page (supported for PDF, XPS, DOCX, PPTX and image output).

    • FitAllColumnsOnOnePage: scale all columns to one page width; rows may extend over multiple pages (supported for DOCX, PPTX and XPS output). FitAllRowsOnOnePage is NOT supported by Aspose.Cells Cloud save options and requesting it returns an error. Returns:

  • The file_uuid of the saved file.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
file_uuidYes
scaling_modeYes
target_formatYes

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",
-  "target_format",
-  "scaling_mode"
-]New value: +[
+  "file_uuid",
+  "target_format",
+  "scaling_mode"
+]
  2. First observedv26.4.0

TDQS

A4.8/5.0
Behavior5/5

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

With no annotations, the description carries the full burden, and it delivers: it discloses that unsupported scaling causes an explicit error rather than silent ignore, documents the exact scaling-mode options and per-mode format support, and notes an unsupported mode returns an error. It also states the return value.

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 purpose is front-loaded, then parameters are cleanly bulleted with no filler. Every sentence adds information an agent needs, including edge-case behavior and return value.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a three-parameter conversion tool with no annotations and no output schema, the description covers what it does, the exact parameter semantics, error behavior, supported scaling options, and return value. Nothing essential is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Input schema has 0% description coverage, but the description fully compensates: file_uuid, target_format, and scaling_mode are each explained, with enumerated values and detailed semantics for each scaling mode including supported output formats.

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 uses a specific verb-resource pair ('Save a spreadsheet in cloud storage to another format') and states the distinguishing purpose: enforcing a print-scaling strategy for page layout. This makes it easy to tell apart from the generic save_spreadsheet_as and conversion siblings.

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?

It gives clear context for when the tool is valuable ('large reports', 'intended page layout instead of truncating content') and explains failure behavior when scaling isn't supported. It doesn't explicitly name alternative tools or when not to use it, so it falls just short of a 5.

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