Aspose.Cells Cloud MCP Server

Official

Overview Schema Source Related Servers Discussions Admin

Add Text At Head

add_text_at_head

Prepends specified text to each text cell in a worksheet range. Uses Aspose.Cells Cloud API to modify Excel cells and returns success status.

Instructions

Adds specified text to the beginning (head) of each text cell 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
`text`	Yes
`_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",
-  "text"
-]New value: +[
+  "file_uuid",
+  "text"
+]

First observedv26.4.0Aug 1, 2026

TDQS

B3.4/5.0

Behavior3/5

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

There are no annotations, so the description carries the full behavioral burden. It does disclose the return value (True on success) and scopes the operation to text cells in a range. However, it does not mention whether the uploaded file is modified in place, permission requirements, or behavior for empty or non-text cells.

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, front-loaded sentence that states the action, scope, and return value efficiently. The phrase 'using Aspose.Cells Cloud API' is somewhat unnecessary, but it does not meaningfully hurt clarity.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The core operation is understandable and the output schema covers return details, so the description is minimally viable. Still, it leaves gaps around optional range/worksheet semantics, file mutation behavior, and when to prefer this over similar text-manipulation tools.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, and the description compensates partially by explaining that text is added to the head of cells and that _range/worksheet define the target area. However, it does not clarify the file_uuid parameter, range format syntax, or default behavior when worksheet or _range are null.

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 specific action: add text to the beginning of each text cell within a range in a worksheet. It names the resource and scope, and the word 'head' distinguishes it from siblings like add_text_at_tail and add_text_before_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?

No guidance is given on when to use this tool versus alternatives such as add_text_before_text or add_text_after_text. With a large sibling set, the agent receives no explicit routing, exclusions, or contextual conditions for choosing this tool.

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

Deploy Server