Aspose.Cells Cloud MCP Server

Official

Overview Schema Source Related Servers Discussions Admin

Remove Custom Characters

remove_custom_characters

Remove user-specified characters from text in an Excel worksheet range, with optional case sensitivity, using Aspose.Cells Cloud API.

Instructions

Removes user-specified custom characters from text values within a specified range of a worksheet in an Excel file using Aspose.Cells Cloud API. Supports case-sensitive or case-insensitive removal. Returns True if the operation succeeds.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`_range`	No
`file_uuid`	Yes
`worksheet`	No
`case_sensitive`	No
`custom_characters`	Yes

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

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 the boolean return value and the scope of removal, but it does not explain whether the file is modified in place, whether the operation is reversible, or how default null values for worksheet and _range behave. For a mutating operation, this is a significant transparency gap.

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 concise, using three sentences that front-load the core action and avoid unnecessary detail. The 'using Aspose.Cells Cloud API' clause adds little practical value for an agent, but overall the structure is efficient.

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 absence of annotations, 0% schema coverage, and a long list of similar removal tools, the description leaves important decision-making details unresolved, particularly parameter defaults and differentiation from remove_* siblings. The existence of an output schema is noted, but the description merely repeats the boolean success result rather than providing richer context.

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 by explaining parameters. It hints at worksheet range and case sensitivity, but it does not specify the expected format of custom_characters, the meaning of null defaults for worksheet and _range, or exactly how case_sensitive changes behavior beyond stating both modes are supported.

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 a specific action and resource: removing user-specified custom characters from text values in an Excel worksheet. It distinguishes itself from numeric, punctuation, and symbol removal by saying 'custom characters', though it does not explicitly differentiate from the sibling remove_text_characters, which may overlap in meaning.

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 the many closely related removal tools such as remove_text_characters, remove_non_printing_characters, or remove_symbols. The description only states what the tool does, never when it should or should not be chosen.

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

Deploy Server