Skip to main content
Glama
WilliamSmithEdward

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

by WilliamSmithEdward
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

List Power Query

xlide_list_queries
Read-onlyIdempotent

List Power Query queries in an Excel workbook to inspect names, groups, load destinations, and applied steps, with paging for large query lists.

Instructions

Lists the Power Query queries in an Excel workbook: name, group, description, where each loads, and its applied step names. If the M formula cannot be parsed, steps is null with steps_error rather than an empty list. Queries live outside the VBA project, so a plain .xlsx has them too. Call this when asked what a workbook does; a workbook with no macros can still be doing most of its work here. Use offset and next_offset to read large query lists in pages.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
offsetNoSkip this many queries before a page.
file_pathYesAbsolute path to the Excel workbook.
max_resultsNoReturn at most this many queries.

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": "Return at most this many queries.",
+  "maximum": 300,
+  "minimum": 1,
+  "title": "Max Results",
+  "type": "integer"
+}
    • addedInput schema / properties / offset
      Added value: +{
+  "default": 0,
+  "description": "Skip this many queries 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 readOnly, idempotent, non-destructive, so safety is covered. The description adds genuinely new behavioral detail: steps is null with steps_error when M formula parsing fails, that queries exist outside the VBA project, and that pagination uses offset/next_offset.

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 what is listed, followed by an edge case, usage guidance, and pagination. Every sentence contributes, though it is slightly denser than strictly necessary.

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?

Given an output schema exists, return values needn't be restated, yet the description still covers the list contents, the parse-failure edge case, and pagination behavior. An agent has everything needed to select and invoke 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 description coverage is 100%, so offset, file_path, and max_results are already documented in the schema. The description only reiterates the offset/next_offset paging pattern, adding minimal meaning beyond the structured fields; baseline 3 applies.

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 and resource ('Lists the Power Query queries in an Excel workbook') and enumerates the fields returned (name, group, description, load targets, step names). This clearly distinguishes it from siblings like xlide_read_query, xlide_list_sheets, and xlide_list_modules.

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 an explicit trigger: 'Call this when asked what a workbook does' and notes that macro-free .xlsx files can still hold most of their work here. It does not name a contrasting alternative (e.g., read_query for a single query's M code), so it stops short of full when/when-not routing.

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