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

Overview Schema Source Related Servers Discussions Admin

Data validation

xlide_manage_validation

DestructiveIdempotent

List, add, or clear Excel data validation rules to control accepted cell values and dropdowns. Set list, numeric, date, time, text length, or custom limits by range or formula.

Instructions

Lists, adds or clears data validation: what a cell will accept, and the dropdown it shows. kind='list' with formula1 as a comma-separated set of values gives a dropdown; kind='list' with a range reference gives one driven by cells. The other kinds take an operator and one or two formulas, which may be literals or references. Validation stops typing in Excel, not writing through this server, and Excel does not re-check cells that already held a value.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`kind`	No	whole, decimal, list, date, time, textLength or custom.	list
`sheet`	Yes	Worksheet name, matched without case.
`action`	No	list, add or clear.	list
`offset`	No	For list: validations to skip.
`formula1`	No	The allowed values. For kind='list', either 'Red,Green,Blue' or a range like $H$1:$H$9. For the others, the bound, such as 0.
`formula2`	No	The second bound, for between and notBetween.
`operator`	No	between, greaterThan, lessThan and so on.	between
`file_path`	Yes	Absolute path to the Excel file.
`cell_range`	No	For add and clear: the range. Empty clears the whole sheet.
`allow_blank`	No	Let the cell be left empty.
`max_results`	No	For list: most to return.
`error_message`	No	What Excel says when the entry is refused.

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": 300,
+  "description": "For list: most to return.",
+  "maximum": 300,
+  "minimum": 1,
+  "title": "Max Results",
+  "type": "integer"
+}

addedInput schema / properties / offset

Added value: +{
+  "default": 0,
+  "description": "For list: validations 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 already flag destructiveHint=true and idempotentHint=true, but the description adds genuinely non-obvious behavior: validation gates typing in Excel and does not apply to writes made through this server, and pre-existing cell values are not re-validated. It does not address permissions, but this is meaningful value 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?

Three dense sentences, no filler, and the critical behavioral caveat is placed last but still earns its space. Slightly heavy on formula semantics for a description, but nothing is wasted.

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?

For a 12-parameter mutation tool with an output schema, the description covers the semantically tricky parts (kind/formula combination and the Excel-side enforcement limit) while the schema and output schema carry the rest. Nothing an agent needs to invoke it correctly appears 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?

With 100% schema description coverage the baseline is 3, and the description earns above it by explaining the two distinct formula1 modes for kind='list' (comma-separated literal set vs. range reference) and the operator/one-or-two-formula pattern for other kinds. It leaves offset, max_results, allow_blank, and error_message to the schema.

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?

Front-loads a precise verb triad (lists/adds/clears) with a specific resource (data validation), then immediately clarifies scope with 'what a cell will accept, and the dropdown it shows.' This is distinguishable from siblings like xlide_manage_conditional_format or xlide_check_cells without opening a schema.

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?

The description explains the semantics of the kind parameter (how list vs. operator-based kinds behave) but never states when this tool is the right choice over adjacent tools like conditional formatting or cell checking, nor any prerequisites. Usage is implied by the parameter walkthrough rather than asserted.

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

Deploy Server