Aspose.Cells Cloud MCP Server

Official

Overview Schema Source Related Servers Discussions Admin

Remove Non Printing Characters

remove_non_printing_characters

Remove invisible control characters from text in an Excel worksheet range via Aspose.Cells Cloud API. Cleans non-printing characters (except tab, newline, carriage return) to ensure data is readable and safe.

Instructions

Removes all non-printing control characters (ASCII 0-31 except tab, newline, carriage return) and other invisible 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
`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.4/5.0

Behavior4/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 mutation, the specific character ranges and exceptions, the one-operation scope, and the success return value. It does not mention side effects like whether the original file is modified or replaced, but for a text-cleaning operation the core behavior is well communicated.

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 compact and action-oriented, with the behavior front-loaded in the first sentence. The only minor waste is the phrase 'using Aspose.Cells Cloud API,' which adds little for tool selection, but overall the description is not 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?

Despite the output schema being present, the description omits important invocation details: default behavior when _range or worksheet are null, expected range formatting, and how this tool differs from many similar text-removal siblings. It conveys intent but is not complete enough for safe, correct invocation.

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 should compensate, but it only loosely maps 'specified range' and 'worksheet' to the _range and worksheet parameters. It does not explain range syntax, the meaning of null defaults, or the role of file_uuid; an agent is left guessing about required argument 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 names a specific action and resource: removing non-printing/invisible characters from text values in a worksheet range of an Excel file. It also specifies the exact character set (ASCII 0-31 except tab, newline, carriage return), which clearly distinguishes it from sibling tools like remove_symbols, trim_text, and remove_extra_line_breaks.

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?

There is no guidance on when to use this tool versus alternatives such as remove_custom_characters, remove_symbols, or remove_text_characters. The use case is only implied by the operation name and description; no explicit when-to-use or when-not-to-use conditions are provided.

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

Deploy Server