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

Overview Schema Source Related Servers Discussions Admin

Write cells

xlide_write_cells

DestructiveIdempotent

Writes a block of values and formulas into an Excel worksheet from a start cell, then saves the file. Handles formulas starting with '=' and preserves untouched content.

Instructions

Writes a rectangular block of values and formulas into a worksheet, starting at one cell, and saves the file. Each row of data is a row of the sheet. A string starting with '=' is written as a formula, as you would type it into Excel 365 with no _xlfn prefixes; anything else is a value. A value written over a formula removes that formula, which is what typing into the cell does. Only the rows you touch are rewritten, so charts, styles, pivot caches and the VBA project are untouched. Ask the user before overwriting cells that hold data. Nothing recalculates until Excel next opens the workbook.

Input Schema

TableJSON Schema

Name	Required	Description
`data`	Yes	Rows of cell values. Numbers, strings, booleans, null for empty, and strings starting with '=' for formulas.
`sheet`	Yes	Worksheet name, matched without case.
`timeout`	No	Seconds allowed if Excel has to do the write.
`file_path`	Yes	Absolute path to the Excel file.
`start_cell`	Yes	Top-left cell of the block, such as B2.

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Sep 20, 2026

TDQS

A4.7/5.0

Behavior5/5

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

Annotations already indicate destructive and non-read-only behavior, but the description adds substantial context: the file is saved, formulas are recognized by '=' prefix, overwriting a formula removes it, only touched rows are rewritten, and nothing recalculates until Excel opens. This goes well beyond the annotations and meaningfully discloses side effects.

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 front-loaded with the core operation and then efficiently covers formula behavior, overwrite semantics, preservation of other workbook content, user consent, and recalculation timing. Every sentence contributes useful information without redundancy.

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 the write operation's complexity, the description covers the essential behavioral context: what is written, how formulas are distinguished, preservation of non-touched content, user-consent requirement, and recalc behavior. An output schema exists, so return-value documentation is not needed. The description is complete for safe and correct invocation.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3, but the description adds real parameter semantics beyond the schema: each row of data maps to a sheet row, formula strings must be written as in Excel 365 without _xlfn prefixes, and non-formula strings are values. This clarifies the data parameter in a way the schema alone does not.

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 specific verb and resource: 'Writes a rectangular block of values and formulas into a worksheet, starting at one cell, and saves the file.' It clearly distinguishes this from read/format/manage siblings by specifying it writes cell content. The scope is unambiguous and actionable.

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?

The description gives clear context for when to use the tool: writing values/formulas into worksheet cell blocks. It also includes an explicit safety guideline: 'Ask the user before overwriting cells that hold data.' It does not explicitly name alternatives or exclusions, so it falls just short of a 5.

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

Deploy Server