Skip to main content
Glama
aspose-cells-cloud

Aspose.Cells Cloud MCP Server

Official
by aspose-cells-cloud
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Remove Extra Line Breaks

remove_extra_line_breaks

Remove excessive line breaks in Excel worksheet text within a chosen range. Collapse multiple newlines into single breaks or eliminate them entirely via Aspose.Cells Cloud.

Instructions

Removes excessive line breaks (multiple consecutive newline characters) from text values within a specified range of a worksheet in an Excel file using Aspose.Cells Cloud API. Collapses multiple line breaks into single line breaks or removes them entirely based on configuration. Returns True if the operation succeeds.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
_rangeNo
file_uuidYes
worksheetNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

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

A3.6/5.0
Behavior3/5

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

With no annotations, the description carries the behavioral burden. It discloses the transformation and the True-on-success return value, but leaves 'configuration' undefined even though no configuration parameter exists in the schema. It also does not state whether the file is modified in place or whether the operation is destructive.

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?

The description is tight and front-loaded: action, scope, and result appear quickly. The added sentence about collapsing versus removing line breaks earns its place, though 'using Aspose.Cells Cloud API' is mildly redundant filler.

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

Completeness3/5

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

The description gives the essential operation and return semantics, and an output schema exists for return details. However, it lacks guidance on optional parameters, range syntax, and the ambiguous configuration behavior, leaving some uncertainty for an agent invoking it correctly.

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 0%, so the description must compensate. It indirectly assigns meaning to _range, worksheet, and file_uuid, but does not specify range format, default behavior when _range or worksheet is null, or how the vague 'configuration' maps to the provided parameters.

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 action ('removes'), a specific resource ('line breaks from text values within a specified range of a worksheet in an Excel file'), and clarifies that it targets 'excessive' breaks rather than all breaks. This distinguishes it from sibling tools like remove_all_line_breaks and trim_text.

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 description implies the use case: cleaning up multiple consecutive newline characters in a worksheet range. However, it does not explicitly name alternatives or state when not to use this tool, such as when all line breaks should be removed or when a different text-cleaning tool is preferable.

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