Aspose.Cells Cloud MCP Server

Official

Overview Schema Source Related Servers Discussions Admin

Convert Number To Text

convert_number_to_text

Convert numeric values in an Excel worksheet range to text strings while preserving formatting. Specify worksheet and range to convert integers, decimals, percentages, currencies, dates, and times.

Instructions

Converts numeric values (integers, decimals, percentages, currencies, dates, times) to text strings within a specified range of a worksheet in an Excel file using Aspose.Cells Cloud API. Preserves formatting and converts to user-readable text representation. Returns True if the operation succeeds.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`_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"
-]New value: +[
+  "file_uuid"
+]
```
First observedv26.4.0Aug 1, 2026

TDQS

A3.5/5.0

Behavior3/5

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

With no annotations, the description carries the disclosure burden; it does state the core behavior, formatting preservation, supported numeric types, and a True return value. However, it does not say whether the operation modifies the original file in place, creates a new file, or what side effects occur, which is significant for a conversion tool.

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?

Three sentences, front-loaded with the core action, followed by behavior and return value. No filler or repetition of readily available schema information.

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?

Although an output schema exists, the description lacks parameter-format details and side-effect information, both of which an agent needs to safely invoke this tool. The supported value types are helpful, but the missing _range/worksheet semantics leave a significant correctness gap.

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 clarify the three parameters. It only loosely references 'range' and 'worksheet' and never explains the required syntax of _range, how worksheet should be named, or the role of file_uuid beyond the name.

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 (converts numeric values to text strings), the object (numeric cells within a range of an Excel worksheet), and even enumerates accepted value types. This clearly distinguishes it from sibling file-conversion tools like convert_excel_to_csv or text-manipulation tools.

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 when to use it - when numeric cells need to become readable text inside a worksheet range - but it never explicitly contrasts it with alternatives or states when not to use it. An agent can infer typical usage but gets no exclusionary guidance.

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

Deploy Server