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

by WilliamSmithEdward

Overview Schema Source Related Servers Discussions Admin

Python

Local

Excel tables

xlide_manage_table

DestructiveIdempotent

List, add, or remove Excel tables to enable structured references and manage table data without broken addresses.

Instructions

Lists, adds or removes Excel tables, the ListObjects that Ctrl+T creates. A table names a block so formulas can say Sales[Amount] instead of an address that breaks when rows move, and it is what a Power Query load writes into. action='list' reads them and changes nothing. Adding one takes the column names from the header row of the range you give. Removing one leaves the cells and takes the table, so structured references to it break.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`sheet`	No	Worksheet. Empty lists every sheet's tables.
`action`	No	list, add or remove.	list
`offset`	No	For list: tables to skip.
`file_path`	Yes	Absolute path to the Excel file.
`cell_range`	No	For add: the range including its header row, such as A1:D20.
`table_name`	No	For add and remove: the table's name.
`totals_row`	No	For add: give the table a totals row.
`max_results`	No	For list: most tables to return.

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedv1.2.2Sep 30, 2026

addedInput schema / properties / max_results

Added value: +{
+  "default": 500,
+  "description": "For list: most tables to return.",
+  "maximum": 500,
+  "minimum": 1,
+  "title": "Max Results",
+  "type": "integer"
+}

addedInput schema / properties / offset

Added value: +{
+  "default": 0,
+  "description": "For list: tables to skip.",
+  "minimum": 0,
+  "title": "Offset",
+  "type": "integer"
+}

First observedv0.1.0Sep 20, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Annotations declare destructiveHint=true and readOnlyHint=false, and the description earns its keep by explaining the actual damage: 'Removing one leaves the cells and takes the table, so structured references to it break.' That is materially useful beyond the hint, though it doesn't cover auth/file-lock or errors.

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 action set, then uses the remaining space for genuinely informative context on tables and the destructive remove behavior. The middle sentence about Power Query is slightly tangential but still short and relevant.

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

Completeness4/5

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

An output schema exists and annotations cover the safety profile, so the description does not need to explain returns. It fills the remaining gaps well: the semantic meaning of a table, per-action effects, and the consequence of removal. Minor absence of pagination context given max_results/offset params.

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 schema already documents every parameter including the 'For list/add/remove' prefixes. The description reinforces that add derives column names from the header row of cell_range, but adds no syntax or format detail beyond the schema's own 'A1:D20' example, so the baseline 3 applies.

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?

Opens with a specific verb set and resource ('Lists, adds or removes Excel tables, the ListObjects'), and immediately grounds it in a concrete concept (Ctrl+T blocks, structured references). It is unmistakably distinct from siblings like xlide_manage_reference or xlide_manage_name.

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?

Explains what each action does and its side effects: 'action=list reads them and changes nothing', add takes column names from the header row, remove leaves the cells. There is clear contextual guidance, though it never names an alternative tool or states explicit when-not-to-use conditions.

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

Deploy Server