Skip to main content
Glama
WilliamSmithEdward

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

by WilliamSmithEdward
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Search VBA

xlide_search_modules
Read-onlyIdempotent

Search every VBA module in an Excel, Word, PowerPoint, or Access file to find where a name is declared or used before editing, with regex and paging.

Instructions

Searches every module's source in an Office file and returns each match with its module, line number and the line itself. Use it to find where a name is declared or used before changing it. content_tokens maps returned module names to tokens for guarded xlide_edit_module calls without a separate read. Use offset and next_offset to page through broad searches; total_match_count counts all matches. Plain text by default; set is_regex for a Python regular expression.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryYesText or pattern to find.
offsetNoSkip this many matches before a page.
is_regexNoTreat query as a regular expression.
file_pathYesAbsolute path to the Office file.
match_caseNoMatch case. Off by default, because VBA itself ignores case.
max_resultsNoReturn at most this many matches.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.2.2
    • changedInput schema / properties / max_results / description
      Previous value: -"Stop after this many matches."New value: +"Return at most this many matches."
    • addedInput schema / properties / offset
      Added value: +{
+  "default": 0,
+  "description": "Skip this many matches before a page.",
+  "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 declare readOnly/idempotent/non-destructive, and the description adds real value on top: the shape of each match, that content_tokens maps module names to tokens usable by guarded xlide_edit_module calls, that total_match_count counts all matches, and that is_regex switches to Python regex semantics. Return-value detail is partly redundant with the output schema, keeping it short of a 5.

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?

Four sentences, each carrying distinct information (purpose, use case, token handoff, paging, regex mode), with the core behavior front-loaded and no 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?

For a read-only search tool with full schema coverage, safety annotations and an output schema, the description covers everything an agent needs: what matches look like, how to page, how to feed results into edits, and query semantics.

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?

Schema coverage is 100%, so the baseline is 3, but the description adds workflow meaning to offset/next_offset paging and clarifies the plain-text versus is_regex query interpretation beyond the terse schema descriptions.

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 precise verb+resource+scope: it searches every module's source in an Office file and returns each match with module, line number and line. This clearly separates it from siblings like xlide_read_module or xlide_list_modules, which retrieve whole modules rather than locate matches.

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 concrete context for use ("find where a name is declared or used before changing it") and explains paging for broad searches. It implies the read_module alternative via "without a separate read" but never names an explicit alternative or says when not to use this tool.

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