Skip to main content
Glama
WilliamSmithEdward

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

by WilliamSmithEdward
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Validate VBA project

xlide_validate_project
Read-onlyIdempotent

Check a VBA project's container for structural issues like mismatched records or missing modules. Call before risky edits; use offset to read later problems from damaged files.

Instructions

Checks a file's VBA project for structural problems: records that disagree with each other, a module the directory names but the container does not hold, and the like. This is about the container, not about the code; use xlide_analyze for the code. Worth calling before risky work on an old or repaired file. Use offset and next_offset to read later problems from a damaged file.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
offsetNoProblems to skip.
file_pathYesAbsolute path to the Office file.
max_resultsNoMost problems to return.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.2.2
    • addedInput schema / properties / max_results
      Added value: +{
+  "default": 300,
+  "description": "Most problems to return.",
+  "maximum": 300,
+  "minimum": 1,
+  "title": "Max Results",
+  "type": "integer"
+}
    • addedInput schema / properties / offset
      Added value: +{
+  "default": 0,
+  "description": "Problems to skip.",
+  "minimum": 0,
+  "title": "Offset",
+  "type": "integer"
+}
  2. First observedv0.1.0

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), so the description's added value is scope and mechanics: it validates the container not the code, and exposes offset/next_offset paging for damaged files. It doesn't state return shape or limits, but the output schema covers that.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three tight sentences with zero filler; the scope statement and sibling routing are front-loaded, and the pre-flight recommendation follows. Every sentence carries information.

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?

With an output schema present, return values need not be explained, and the description covers purpose, boundaries, sibling routing, and paging. Nothing needed to invoke this correctly is missing.

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 file_path, offset, and max_results are already documented. The description only adds that offset/next_offset are for paging through problems in a damaged file, which is a marginal gain over the schema's 'Problems to skip.'

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+resource (checks a file's VBA project for structural problems) and enumerates concrete failure classes (cross-record disagreement, directory-named module missing from container). It explicitly separates itself from xlide_analyze, which is about code rather than container.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Names the alternative (xlide_analyze) and the condition that selects it, and gives a proactive trigger ('worth calling before risky work on an old or repaired file'). Nothing about when to reach for this tool is left to inference.

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

Deploy Server

Other Tools