Aspose.Cells Cloud MCP Server

Official

Overview Schema Source Related Servers Discussions Admin

Remove Before Text

remove_before_text

Removes all characters before a specified delimiter in worksheet cells, with optional range filtering and case sensitivity, returning success status.

Instructions

Removes all characters before (to the left of) a specified delimiter text within each text cell in a worksheet range using Aspose.Cells Cloud API. Returns True if the operation succeeds.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`text`	Yes
`_range`	No
`file_uuid`	Yes
`worksheet`	No
`case_sensitive`	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",
-  "text"
-]New value: +[
+  "file_uuid",
+  "text"
+]

First observedv26.4.0Aug 1, 2026

TDQS

C2.9/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 behavioral burden. It discloses the mutating effect and success return, but leaves out important behavior such as case-sensitive matching, behavior when the delimiter is absent, whether the file is modified in place, and how worksheet/_range scoping works.

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?

A single sentence with the core action front-loaded and no filler. It is appropriately concise, though it sacrifices useful behavioral and parameter detail.

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 five parameters, no annotations, and no schema descriptions, the description is too thin for reliable invocation. It does not cover parameter semantics, edge cases, or scoping behavior, even though an output schema exists.

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%, and the description only clarifies that text is a delimiter and that text cells are affected. Required file_uuid, case_sensitive, worksheet, and _range are not explained, so an agent cannot reliably determine valid values or effects.

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 operation (removes all characters before a delimiter), the resource (each text cell in a worksheet range), and the direction (to the left of), which clearly sets it apart from siblings like remove_after_text.

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 choose this tool over its many text-manipulation siblings such as remove_after_text, remove_custom_characters, or trim_text. The operation is implied by the description, but no conditions, exclusions, or alternatives are stated.

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

Deploy Server