Skip to main content
Glama
aspose-cells-cloud

Aspose.Cells Cloud MCP Server

Official
by aspose-cells-cloud
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Remove Text Characters

remove_text_characters

Remove alphabetic characters from selected cells in Excel worksheets while retaining numeric and symbolic content.

Instructions

Removes all text/alphabetic characters (A-Z, a-z) from cells within a specified range of a worksheet in an Excel file using Aspose.Cells Cloud API, preserving numbers, symbols, and whitespace. 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

B3.2/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It mentions the operation and the True return value, but does not disclose whether the original file is modified in place, what happens when optional parameters like _range or worksheet are omitted, or error/edge-case behavior. This is a significant gap for a tool with no annotation safety hints.

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 two sentences and front-loads the core action before context. It is compact and readable, though the mention of 'using Aspose.Cells Cloud API' adds only marginal value for an agent deciding how to call the tool.

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?

With no annotations and 0% schema coverage, the description should carry more weight. It does not specify default behavior for optional parameters, exact range format, side effects on the file, or failure behavior. An output schema exists, but that does not compensate for missing operational context needed to call the tool correctly.

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 for missing parameter documentation. It broadly hints at the roles of file_uuid, worksheet, and _range, but does not explain range syntax, defaults, or how the optional parameters interact. The parameter names are somewhat self-explanatory, but the description does not add enough semantic detail to fully guide invocation.

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 verb and resource: removes alphabetic characters (A-Z, a-z) from cells in a worksheet range. It explicitly states what is preserved (numbers, symbols, whitespace), which differentiates it clearly from sibling tools like remove_numeric_characters and remove_symbols.

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 tool should be used when alphabetic characters need to be removed from Excel cells, and the preservation clause helps distinguish it from sibling removal tools. However, it provides no explicit when-to-use, when-not-to-use, or alternative tool guidance, leaving selection partially to inference.

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