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

Overview Schema Source Related Servers Discussions Admin

Access tables and queries

xlide_access_catalog

Read-onlyIdempotent

Lists Access tables, columns, saved queries with SQL, and relationships to show full schema beyond VBA code. Use it to page through large catalogs or inspect table links.

Instructions

Lists what an Access database holds besides its code: tables with their columns, saved queries with their SQL, and the relationships between tables. An .accdb is an application rather than a document, and the VBA in it is written against these, so reading the modules alone shows half of it. Use include with offset and next_offsets to page through a large catalog. Long query SQL is previewed; use xlide_read_access_query for the whole text. If one query's SQL cannot be read, that entry has sql=null and sql_error rather than hiding the catalog. Access files only.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`offset`	No	Items to skip in each list.
`include`	No	'tables', 'queries', 'relationships' or 'all'.	all
`file_path`	Yes	Absolute path to the Access database.
`max_results`	No	Most items per list.
`include_system`	No	Include the MSys tables and relationships Access keeps its own objects in. Off by default: every database has them, and listing them buries the few that are about the user's data.

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedv1.2.2Sep 30, 2026

addedInput schema / properties / max_results

Added value: +{
+  "default": 300,
+  "description": "Most items per list.",
+  "maximum": 500,
+  "minimum": 1,
+  "title": "Max Results",
+  "type": "integer"
+}

addedInput schema / properties / offset

Added value: +{
+  "default": 0,
+  "description": "Items to skip in each list.",
+  "minimum": 0,
+  "title": "Offset",
+  "type": "integer"
+}

First observedv0.1.0Sep 20, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already declare read-only, idempotent and non-destructive, so safety is covered. The description goes further by disclosing failure semantics ('that entry has sql=null and sql_error rather than hiding the catalog') and the default exclusion of system tables, which the annotations do not convey.

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 what, then paging, then the sibling escape hatch, then the error contract. Efficient overall, though the 'An .accdb is an application rather than a document...' sentence is motivational exposition that could be trimmed.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/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, and the description still covers the notable output contract (sql=null/sql_error, next_offsets). Nothing an agent needs to invoke it correctly is missing; remaining detail lives in the schema.

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 include, offset, max_results and file_path are already documented with defaults and ranges. The description reinforces the paging pattern and mentions next_offsets, but adds no syntax or format detail beyond the schema, so the 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 three concrete resources (tables with columns, saved queries with SQL, table relationships) and explicitly frames the scope as 'what an Access database holds besides its code'. This is clearly distinguishable from siblings like xlide_list_modules and xlide_read_access_query.

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 an alternative and the condition that selects it ('Long query SQL is previewed; use xlide_read_access_query for the whole text'), explains paging via include/offset/next_offsets, and gives an explicit applicability constraint ('Access files only'). Removes guesswork about when to call it.

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

Deploy Server