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 (ListObjects) to enable structured references like Sales[Amount] for stable formulas.

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
`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.

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.6/5.0

Behavior5/5

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

Annotations already declare readOnlyHint=false and destructiveHint=true, and the description adds materially: list is read-only, adding derives column names from the header row, and removing leaves the cells intact while breaking structured references. This discloses the real consequence of deletion beyond the boolean hint.

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?

Four sentences, front-loaded with the operation and entity, and each sentence adds a distinct piece: definition, rationale, action semantics, and removal side effect. The formula/Power Query background is slightly expository but remains relevant and concise.

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 three-action tool with six parameters, the description plus annotated schema covers prerequisites (header row for add, empty sheet meaning all tables), side effects (structured references break), and read-only list behavior. The output schema covers return values, so nothing needed for correct invocation 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?

All six parameters are fully documented in the input schema, so the baseline is 3. The description adds value by linking action values to parameter roles: cell_range must include the header row, and table_name is used for add and remove while preserving cells. This supplements the schema without redundancy.

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 opens with a precise verb-resource pair: 'Lists, adds or removes Excel tables' and identifies the entity as 'the ListObjects that Ctrl+T creates.' This clearly distinguishes Excel tables from sheets, names, or modules handled by sibling tools.

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 contextual signals for when the tool is relevant, noting that tables are what Power Query loads write into and that action='list' reads and changes nothing. It does not name alternative sibling tools explicitly, so it stops short of full when-to-use-versus-alternative guidance.

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

Deploy Server