xlsx-tools-mcp

Overview Schema Source Related Servers Discussions Admin

delete_columns

Remove one or more columns from an .xlsx sheet and shift the remaining columns left, with optional LibreOffice recalculation after saving.

Instructions

Delete columns, shifting the columns to their right leftward.

Set recalculate=False to skip the LibreOffice recompute (e.g. for structurally complex workbooks you don't want round-tripped).

Args: path: Path to the .xlsx file, or the name of a preloaded file. Omit if only one file is configured. sheet: Sheet name. start_column: 1-based column index to start deleting from. count: Number of columns to delete. recalculate: Run the LibreOffice recompute pass after saving.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`path`	No
`count`	No
`sheet`	Yes
`backup`	No
`recalculate`	No
`start_column`	Yes

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv0.3.0Oct 4, 2026

addedInput schema / properties / backup

Added value: +{
+  "anyOf": [
+    {
+      "type": "boolean"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Backup"
+}

First observedv0.1.0Aug 17, 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 full burden. It usefully discloses the column-shift semantics and the LibreOffice recompute pass with its opt-out, but never states that deletion is destructive/irreversible or what the 'backup' parameter does — significant omissions for a mutation tool.

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-loaded with the operation and its effect, then a clean Args block. The parenthetical on recalculate is slightly wordy but earns its place by explaining the rationale rather than padding.

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

Completeness3/5

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

An output schema exists so return values need no explanation, and the recompute behavior is covered. However, for a destructive operation with zero annotations, the description should flag irreversibility and document the undocumented 'backup' parameter.

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 description coverage is 0%, so the description must compensate, and it does for 5 of 6 parameters, including the 1-based indexing semantics of start_column and the default behavior of count and recalculate. It omits 'backup' entirely, which is the one remaining gap.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb+resource ('Delete columns') and adds the mechanical consequence ('shifting the columns to their right leftward'), which distinguishes it from insert_columns/delete_rows behaviorally. It does not explicitly name those siblings, so it stops short of a 5.

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?

Gives a concrete when-to-use condition for one parameter ('Set recalculate=False ... e.g. for structurally complex workbooks you don't want round-tripped'), but offers no guidance on when to choose this over insert_columns, delete_rows, or clear_range, and no prerequisites.

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