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

Overview Schema Source Related Servers Discussions Admin

Copy or paste cells

xlide_copy_cells

DestructiveIdempotent

Copies an Excel range to another cell or block, on the same or another sheet, applying Paste Special options and saving the workbook. Use it to duplicate, transpose, or merge data safely.

Instructions

Copies a range to another cell or block, on the same sheet or another sheet, and saves the workbook. Paste Special can select values, formulas, formats, comments, validation, links or other parts; it can also transpose, skip blanks or combine values arithmetically. The destination may hold data, which the paste can replace. Set allow_overwrite=true only after the user agrees to replace it. Formulas and their relative references move as Excel's Copy does. Works on .xlsx, .xlsm and .xlam.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`paste`	No	all, values, formulas, formats, comments, validation, link, or another Excel Paste Special kind.	all
`sheet`	Yes	Source worksheet name.
`file_path`	Yes	Absolute path to the Excel file.
`operation`	No	add, subtract, multiply or divide; empty replaces.
`transpose`	No	Turn source rows into destination columns.
`destination`	Yes	Destination cell or repeatable block.
`skip_blanks`	No	Leave destination cells unchanged for blank source cells.
`source_range`	Yes	Source range such as A1:D20.
`allow_overwrite`	No	Required: the paste may replace data. Set after user agreement.
`destination_sheet`	No	Destination sheet; empty means the source sheet.

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Addedv1.2.2Sep 30, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Annotations already flag destructiveHint=true and idempotentHint=true, and the description reinforces this by disclosing that the destination may hold data that the paste can replace and that overwrite requires user consent. It further adds non-obvious behavior: formulas move with relative references as Excel's Copy does, and it works on .xlsx/.xlsm/.xlam. This is rich context beyond the annotations.

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 what the tool does, then layers paste-special options, overwrite warning, and formula semantics. Every sentence carries information, though the paste-special enumeration is dense and could be trimmed slightly.

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 10-parameter mutation tool with an output schema already present, the description covers the essential gaps: overwrite consent, formula reference behavior, supported file types, and paste mode semantics. An agent has enough to invoke it correctly and safely.

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. The description nonetheless adds interpretive meaning, e.g. that 'operation' combines values arithmetically and that skip_blanks leaves destination cells untouched, which helps an agent understand the paste-mode interaction rather than just the field list.

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 ('copies a range to another cell or block, on the same sheet or another sheet') and adds a side effect ('saves the workbook'). This is clearly distinguishable from siblings like xlide_write_cells and xlide_read_cells without opening any 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 explicit conditional guidance for the risky path: 'Set allow_overwrite=true only after the user agrees to replace it.' It also explains when paste variants apply (values/formulas/formats/etc.). It stops short of naming sibling alternatives such as write_cells for outright value entry, so it is not a full when/when-not map.

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

Deploy Server