Aspose.Cells Cloud MCP Server

Official

Overview Schema Source Related Servers Discussions Admin

Remove Last N Characters

remove_last_n_characters

Remove trailing characters from text cells in an Excel range. Specify the number to strip and the worksheet range to truncate cell contents using Aspose.Cells Cloud.

Instructions

Removes the last N characters from the end of each text cell within a specified range of a worksheet in an Excel file using Aspose.Cells Cloud API. Returns True if the operation succeeds.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`_range`	No
`number`	Yes
`file_uuid`	Yes
`worksheet`	No

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedv26.4.1Sep 18, 2026

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",
-  "number"
-]New value: +[
+  "file_uuid",
+  "number"
+]

First observedv26.4.0Aug 1, 2026

TDQS

C2.7/5.0

Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It mentions that the operation targets text cells and returns True on success, but it does not reveal whether the original file is modified in-place, how missing optional parameters affect behavior, what happens to non-text cells, or whether any permissions or side effects are involved. This is a significant transparency gap for a mutation-style operation.

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 a single concise sentence with no filler, and it front-loads the core action before mentioning the API and return value. It earns its length, though it could use the available space to add missing parameter and behavioral context without becoming bloated.

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

Completeness2/5

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

Given four parameters, zero schema descriptions, no annotations, and a simple output schema, the description is not complete enough for safe invocation. It lacks essential context about optional parameters, default behavior, whether the file is overwritten, and how to handle the operation at scale. The description covers the basic action but leaves too many operational details unspecified.

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

Parameters2/5

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

Schema description coverage is 0%, so the description must compensate, but it only provides partial parameter semantics. It maps 'N' to the number parameter and references 'specified range' and 'worksheet,' but it does not clarify the optional parameters' defaults or behavior when omitted (e.g., _range defaults to null, worksheet defaults to null). The description may even mislead because it implies a range is always specified when _range is not required.

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?

The description clearly states the action: removes the last N characters from each text cell within a specified range of a worksheet. It identifies the resource (Excel worksheet cells via Aspose.Cells Cloud API) and the operation, which is sufficient to understand the tool's core purpose. However, it does not explicitly distinguish itself from closely related siblings like remove_first_n_characters or trim_text, so it falls short of full sibling differentiation.

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

Usage Guidelines2/5

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

The description provides no guidance on when to use this tool versus alternatives such as remove_first_n_characters, trim_text, or remove_custom_characters. It does not mention prerequisites, default behavior when optional parameters are omitted, or any conditions that would make this tool the preferred choice. Users must infer usage solely from the name and action description.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server