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

Overview Schema Source Related Servers Discussions Admin

Write cells

xlide_write_cells

DestructiveIdempotent

Write a block of values or formulas into an Excel worksheet at a specified start cell and save the file. Overwrites are blocked unless allow_overwrite is true.

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 cell given as {"rich_text": [{"text": "Total ", "bold": true}, {"text": "42"}]} is text in more than one font. A value written over a formula removes that formula, which is what typing into the cell does. On .xlsx, .xlsm and .xlam, only the touched worksheet rows are rewritten; their cached formula results remain stale until Excel opens the file or xlide_read_cells calculates them in memory. Writing .xlsb cells needs Windows with Excel, which recalculates and saves the workbook. Writing .xls cells is not offered. Cells that hold data are refused until allow_overwrite=true; ask the user first.

Input Schema

TableJSON Schema

Name	Required	Description
`data`	Yes	Rows of cell values. Numbers, strings, booleans, null for empty, strings starting with '=' for formulas, and {"rich_text": [runs]} for text in several fonts, each run a text with any of bold, italic, strike, underline, size, font, color (RRGGBB) and script.
`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.
`allow_overwrite`	No	Allow replacing cells that already hold data or formulas. Ask the user first. Without it, the write is refused before saving.

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

addedInput schema / properties / allow_overwrite

Added value: +{
+  "default": false,
+  "description": "Allow replacing cells that already hold data or formulas. Ask the user first. Without it, the write is refused before saving.",
+  "title": "Allow Overwrite",
+  "type": "boolean"
+}

Changed1 schema field changedv1.1.0Sep 24, 2026

changedInput schema / properties / data / description

Previous value: -"Rows of cell values. Numbers, strings, booleans, null for empty, and strings starting with '=' for formulas."New value: +"Rows of cell values. Numbers, strings, booleans, null for empty, strings starting with '=' for formulas, and {\"rich_text\": [runs]} for text in several fonts, each run a text with any of bold, italic, strike, underline, size, font, color (RRGGBB) and script."

First observedv0.1.0Sep 20, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Annotations already declare destructiveHint=true and idempotentHint=true, and the description adds substantial context beyond them: overwriting a formula removes it, only touched rows are rewritten, cached formula results stay stale until Excel opens the file or xlide_read_cells recalculates, and platform constraints for .xlsb/.xls. This is genuinely useful behavioral disclosure.

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 write semantics and overwrite guard are front-loaded, and every sentence carries information (formula handling, rich text, staleness, platform support). It is on the long side but dense rather than padded, so no sentence is wasted.

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?

For a mutation tool with an output schema present, the description covers the safety gate (allow_overwrite), the formula/value interpretation, platform limitations, and post-write staleness behavior. Nothing an agent needs before invoking it correctly is missing.

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 interpretation rules the schema only gestures at: a string starting with '=' becomes a formula with no _xlfn prefixes, and the rich_text run shape is illustrated with a concrete example. Minor extra value over the schema, not a full replacement for its documentation.

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 ('Writes a rectangular block of values and formulas into a worksheet, starting at one cell, and saves the file'), with scope detail that separates it from xlide_read_cells and xlide_format_cells. An agent knows exactly what operation this is without opening the schema.

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 concrete conditions: cells holding data are refused until allow_overwrite=true and the user must be asked first; .xlsb needs Windows with Excel; .xls writing is not offered. It does not explicitly name sibling alternatives (copy_cells, format_cells, sort_rows) for adjacent tasks, so it stops short of full routing guidance.

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

Deploy Server