Aspose.Cells Cloud MCP Server

Official

Overview Schema Source Related Servers Discussions Admin

Word Case

word_case

Convert text in an Excel worksheet range to uppercase, lowercase, title case, sentence case, or toggle case using Aspose.Cells Cloud API.

Instructions

Converts text case (uppercase, lowercase, title case, sentence case, or toggle case) 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	Default
`_range`	No
`file_uuid`	Yes
`worksheet`	No
`word_case_type`	No	UpperCase

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.1/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 that it returns True on success, but it does not state whether the operation modifies the original file, is destructive/reversible, requires specific permissions, or has rate limits. For a mutation tool, this is a significant gap.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single sentence that is front-loaded with the verb and purpose, lists the supported case types, and mentions the return value. Every phrase adds value and there is no wasted text.

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 tool has 4 parameters, no annotations, and only a minimal output schema, the description is too sparse. It does not explain parameter formats, edge cases, or side effects, which an agent would need to invoke it correctly. The one-sentence description is insufficient for a file-modifying operation.

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 parameter meanings. It hints at 'range' and 'worksheet' and lists case types, but it does not explicitly map these to parameters (_range, worksheet, word_case_type) nor explain file_uuid or the expected format of _range. The description adds some context but not enough to cover the low schema coverage.

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 states a clear verb ('Converts') and resource ('text case ... within a specified range of a worksheet in an Excel file') and explicitly lists the case options. It is distinct from sibling tools like trim_text or convert_excel_to_json, none of which perform case conversion.

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?

The description gives no guidance on when to use this tool versus alternatives, no conditions, and no exclusions. It simply states what it does without explaining when one might prefer it over other text manipulation tools.

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

Deploy Server