Skip to main content
Glama
WilliamSmithEdward

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

by WilliamSmithEdward
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

List Office files

xlide_list_projects
Read-onlyIdempotent

Lists Office and VB6 project files in the workspace, returning paths, host apps, and VBA openability to help identify a file when none is named.

Instructions

Finds the Office files in this server's workspace and returns their absolute paths, host application and whether their VBA can be opened. Call this first when the user has not named a file. Covers Excel (.xlsm, .xlsb, .xlam, .xls, and .xlsx for Power Query and sheets), Word (.docm, .dotm, .doc), PowerPoint (.pptm, .potm), Access (.accdb, .mdb), and Visual Basic 6 projects (.vbp, whose modules are the files its manifest names). Files whose extension is recognized but not openable are listed with the reason, so a template or add-in is not silently missing. Use offset and next_offset to read large workspaces in pages.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
offsetNoSkip this many files before a page.
subfolderNoLimit the search to this folder. Empty searches every workspace root.
max_resultsNoReturn at most this many files.

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": 2000,
+  "description": "Return at most this many files.",
+  "maximum": 2000,
+  "minimum": 1,
+  "title": "Max Results",
+  "type": "integer"
+}
    • addedInput schema / properties / offset
      Added value: +{
+  "default": 0,
+  "description": "Skip this many files before a page.",
+  "minimum": 0,
+  "title": "Offset",
+  "type": "integer"
+}
  2. First observedv0.1.0

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, non-destructive, closed-world behavior. The description adds context those annotations cannot: the exact return fields, the fact that recognized-but-unopenable files are listed with a reason so templates/add-ins are not silently dropped, and the paging contract. It omits auth/permission notes, keeping it below 5.

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 core action and return shape, then the when-to-use rule, then supported formats, then edge-case behavior and pagination. The extension enumeration is long but genuinely informative for file-type expectations; nothing is filler.

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?

An output schema exists, so return values need not be explained in prose, yet the description still clarifies the semantics of the openability field and the 'listed with reason' edge case. Together with the covered file-type matrix and paging guidance, an agent has everything needed to call it correctly.

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 coverage is 100%, so offset, subfolder, and max_results are already documented in the schema. The description only restates pagination ('offset and next_offset') and even references a next_offset field that is not an input parameter. Baseline 3 is appropriate.

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 (finds/lists) and resource (Office files in this workspace) and specifies the return payload: absolute paths, host application, and VBA openability. It is clearly distinguishable from siblings like xlide_list_modules or xlide_list_sheets, which enumerate different resources.

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?

Gives explicit invocation guidance: 'Call this first when the user has not named a file,' which is a real routing rule. It also explains pagination via offset/next_offset. It stops short of naming the sibling alternative an agent should use once a file *is* named, so it is not a 5.

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