xlide-excel-word-powerpoint-access-office-vba-mcp

Overview Schema Source Related Servers Discussions Admin

Read cells

xlide_read_cells

Read-onlyIdempotent

Read a range of Excel worksheet cells as values, formulas, both, or displayed text; optionally calculate formulas in memory, returning a grid up to 20,000 cells.

Instructions

Reads a range of cells from a worksheet and returns a grid of values, formulas, both, or the text each cell shows under its number format. On .xlsx, .xlsm and .xlam, values are what Excel last calculated and stored; calculate=true works formulas out in memory with pyOfficeEditor's engine and names cells it could not work out. A failed formatted or rich-text read names the cell and refuses rather than returning an empty value. On .xlsb and .xls, Windows with Excel is required and only calculated values are available, not formulas or formatted text. A partial grid from Excel is refused. At most 20,000 cells per call.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`sheet`	Yes	Worksheet name, matched without case.
`include`	No	'values', 'formulas', 'both', 'text' for what each cell shows, such as 12.5% or 1/15/2024, or 'rich_text' for the font runs of text written in more than one font.	values
`timeout`	No	Seconds allowed if Excel has to answer.
`calculate`	No	For .xlsx, .xlsm and .xlam, work formulas out in memory before reading. The file is not changed. Binary .xlsb and .xls reads use Excel instead.
`file_path`	Yes	Absolute path to the Excel file.
`cell_range`	Yes	A1-style range, such as A1:D50, or a single cell.

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv1.2.2Sep 30, 2026

changedInput schema / properties / calculate / description

Previous value: -"Work every formula out before reading, with the formula engine. The file is not changed. Use it after writing inputs, to see the results now."New value: +"For .xlsx, .xlsm and .xlam, work formulas out in memory before reading. The file is not changed. Binary .xlsb and .xls reads use Excel instead."

Changed2 schema fields changedv1.1.0Sep 24, 2026

addedInput schema / properties / calculate

Added value: +{
+  "default": false,
+  "description": "Work every formula out before reading, with the formula engine. The file is not changed. Use it after writing inputs, to see the results now.",
+  "title": "Calculate",
+  "type": "boolean"
+}

changedInput schema / properties / include / description

Previous value: -"'values', 'formulas' or 'both'."New value: +"'values', 'formulas', 'both', 'text' for what each cell shows, such as 12.5% or 1/15/2024, or 'rich_text' for the font runs of text written in more than one font."

First observedv0.1.0Sep 20, 2026

TDQS

A4.4/5.0

Behavior5/5

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

Annotations already declare readOnly/idempotent/non-destructive, and the description layers on substantial extra context: what 'values' means on modern vs binary formats, that calculate works formulas in memory without modifying the file, that unresolved cells are named, that failed formatted/rich-text reads refuse rather than return empty, that partial Excel grids are refused, and a 20,000-cell cap.

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?

Front-loads the core purpose in the first clause before detailing format-specific caveats. Dense but every sentence carries real information; only the repeated emphasis on file-format behavior costs a little length.

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

Completeness5/5

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

Given an existing output schema, the description need not explain return shape, and it instead completes the picture with format support, calculation semantics, failure behavior, and a size limit. Nothing an agent needs to call it correctly is missing.

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 100%, so the baseline is 3 and the description largely restates schema content (include modes, calculate behavior, cell_range format). It adds only marginal semantics beyond the schema, such as naming cells whose formulas could not be worked out.

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?

States a specific verb and resource ('Reads a range of cells from a worksheet') and enumerates the return modes (values, formulas, both, formatted text). It is unmistakably distinct from siblings like xlide_write_cells and xlide_check_cells.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives clear usage conditions: calculate=true only helps on .xlsx/.xlsm/.xlam, and .xlsb/.xls require Windows with Excel and yield calculated values only. It does not explicitly route the agent to alternative siblings (e.g., check_cells for validation or evaluate_formula for a single formula), so it stops short of full when/when-not guidance.

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

Deploy Server