Skip to main content
Glama
WilliamSmithEdward

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

by WilliamSmithEdward
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Read Power Query

xlide_read_query
Read-onlyIdempotent

Read a Power Query M formula and its metadata from an Excel workbook, including description, group, load target, and refresh settings. Supports reading line ranges and reports step errors.

Instructions

Reads one query's M formula, with its description, group, load target and refresh settings. The formula is the let ... in expression as the Advanced Editor shows it. start_line and end_line read a slice of a long formula; the content_token always describes the whole query. If applied steps cannot be read, steps is null and steps_error gives the reason; the M formula remains available.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
end_lineNoLast formula line. 0 means the end.
file_pathYesAbsolute path to the Excel workbook.
query_nameYesQuery name, matched without case.
start_lineNoFirst formula line. 0 means the start.

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 / end_line
      Added value: +{
+  "default": 0,
+  "description": "Last formula line. 0 means the end.",
+  "minimum": 0,
+  "title": "End Line",
+  "type": "integer"
+}
    • addedInput schema / properties / start_line
      Added value: +{
+  "default": 0,
+  "description": "First formula line. 0 means the start.",
+  "minimum": 0,
+  "title": "Start Line",
+  "type": "integer"
+}
  2. First observedv0.1.0

TDQS

A4.4/5.0
Behavior5/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive), and the description still adds real behavior: slice semantics for start_line/end_line, the fact that content_token always describes the whole query, and the failure mode where steps is null with steps_error while the formula remains readable. That is exactly the extra context that annotations cannot carry.

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 the tool's purpose and ending with the error behavior. Dense but every sentence carries a distinct fact; only the metadata enumeration in sentence one borders on listy.

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-value documentation is not required, yet the description still explains the steps/steps_error fallback path. For a read-only, four-parameter tool with full schema coverage, nothing an agent needs to call it correctly is 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?

Schema coverage is 100%, so the baseline is 3, but the description goes further by explaining what a line slice means in relation to the whole-query content_token — a semantic distinction the schema's '0 means the start/end' does not convey.

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?

The description names a specific verb and resource ('Reads one query's M formula') and enumerates exactly what comes back (description, group, load target, refresh settings). It is clearly distinguishable from xlide_list_queries and xlide_write_query without opening either 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?

Usage is implied by 'one query' versus the sibling list tool, and the start_line/end_line note hints at the long-formula case, but the description never explicitly states when to choose this over xlide_list_queries or xlide_read_module. No exclusions or prerequisites are given.

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