Aspose.Cells Cloud MCP Server

Official

Overview Schema Source Related Servers Discussions Admin

Trim Text

trim_text

Remove unwanted leading and trailing characters from text values in a specified Excel worksheet range via cloud API, returning operation success.

Instructions

Removes specified leading and trailing characters from text values 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
`file_uuid`	Yes
`trim_text`	No
`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"
-]New value: +[
+  "file_uuid"
+]
```
First observedv26.4.0Aug 1, 2026

TDQS

B3.2/5.0

Behavior2/5

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

With no annotations provided, the description carries full burden. It discloses the return value ('Returns True if the operation succeeds') and invokes the Aspose.Cells Cloud API, but it does not indicate whether the operation modifies the file in place, any required permissions, failure behavior, or side effects. This is a significant gap for a write 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 compact sentence with no unnecessary words. It front-loads the core action and includes a return-value note, which is efficient for a tool with few parameters. However, it omits parameter details that would be necessary for correctness, so it sacrifices completeness for brevity.

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 the tool deals with a specific Excel range, worksheet, and custom characters, and has 4 parameters with zero schema coverage, the description is far from complete. It does not explain the parameters, which leaves an agent unable to construct a valid call. While an output schema exists, parameters remain undefined, making the description inadequate.

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 clarify parameter meanings, but it does not. It mentions 'specified leading and trailing characters' and 'within a specified range of a worksheet,' hinting at trim_text and _range/worksheet, but it never names or explains the parameters. An agent would not know what to pass for file_uuid, trim_text, _range, or worksheet.

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 clearly states the action ('Removes specified leading and trailing characters') and the target ('text values within a specified range of a worksheet in an Excel file'). It distinguishes itself from siblings like trim_text_from_leading and trim_text_from_trailing by explicitly covering both ends, and from other removal tools by focusing on trimming rather than removal of specific character types.

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 usage when both leading and trailing characters need to be trimmed, which is implied but not explicitly contrasted with single-sided alternatives. It offers no guidance on when not to use it or mention of alternative tools like trim_text_from_leading or trim_text_from_trailing, leaving the agent to infer the distinction.

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

Deploy Server