Skip to main content
Glama
WilliamSmithEdward

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

by WilliamSmithEdward
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Defined names

xlide_manage_name
DestructiveIdempotent

List, add, or remove Excel workbook defined names to simplify formulas and VBA references. Specify file path and name details.

Instructions

Lists, adds or removes a workbook's defined names. A defined name is what lets a formula say TaxRate rather than Config!$B$7, and VBA reads them too, so removing one can break code as well as formulas. action='list' changes nothing. For a range, qualify refers_to with its sheet and use absolute addresses to avoid following the active sheet or moving with a copied formula, for example Data!$A$1:$A$50.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameNoFor add and remove: the defined name.
scopeNoA sheet name to scope it to that sheet. Empty means the workbook.
actionNolist, add or remove.list
offsetNoFor list: names to skip.
file_pathYesAbsolute path to the Excel file.
refers_toNoFor add: what it points at, such as Data!$A$1:$A$50.
max_resultsNoFor list: most names to return.

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": "For list: most names to return.",
+  "maximum": 300,
+  "minimum": 1,
+  "title": "Max Results",
+  "type": "integer"
+}
    • addedInput schema / properties / offset
      Added value: +{
+  "default": 0,
+  "description": "For list: names to skip.",
+  "minimum": 0,
+  "title": "Offset",
+  "type": "integer"
+}
  2. First observedv0.1.0

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and idempotentHint=true, but the description adds real value: removing a name can break VBA code as well as formulas, and list is a no-op. That is exactly the kind of consequence detail annotations cannot 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?

Three sentences, front-loaded with the action scope, then the risk caveat, then the refers_to guidance. No filler, though the middle clause about VBA is slightly dense and could be tighter.

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?

With an output schema present, return values need no explanation, and the description covers the destructive caveat and the non-obvious refers_to construction. Complete enough for a 7-param mutation tool, though permission/auth prerequisites are unstated.

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 baseline is 3, but the description meaningfully extends refers_to semantics beyond the schema's terse example by warning to qualify with the sheet and use absolute addresses to avoid active-sheet/copy drift. That adds meaning the schema does not.

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 set (lists/adds/removes) and resource (workbook defined names) in the first sentence, and it is clearly distinguishable from siblings like xlide_manage_reference or xlide_manage_table. An agent knows immediately what domain this touches.

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?

Clarifies the per-action semantics ('action=list changes nothing') and gives concrete guidance for constructing refers_to when adding a range. It does not explicitly name a sibling alternative or state when this tool should NOT be used, which keeps it short of 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