Skip to main content
Glama
WilliamSmithEdward

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

by WilliamSmithEdward
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Delete module

xlide_delete_module
Destructive

Permanently delete a VBA module from an Office file and save the change. No undo; read the module first so it can be restored if needed.

Instructions

Permanently deletes a VBA module from an Office file and saves it. There is no undo: ask the user first, and read the module before deleting it so its code can be put back if they change their mind. Document modules cannot be deleted. For Excel, the write is refused if the server cannot check whether a shape still calls the module.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
file_pathYesAbsolute path to the Office file.
module_nameYesModule to delete.
allow_protectedNoPermit saving a password-protected VBA project. Set true only after the user agrees.
expected_content_tokenNoThe content_token from your read, so a module that changed since is not deleted on the strength of a stale look at it.
allow_invalidate_signatureNoPermit saving a change that removes the VBA project's digital signature, where applicable. Set true only after the user agrees.

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 / allow_invalidate_signature / description
      Previous value: -"Ask the user first."New value: +"Permit saving a change that removes the VBA project's digital signature, where applicable. Set true only after the user agrees."
    • changedInput schema / properties / allow_protected / description
      Previous value: -"Ask the user first."New value: +"Permit saving a password-protected VBA project. Set true only after the user agrees."
  2. First observedv0.1.0

TDQS

A4.7/5.0
Behavior5/5

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

Goes well beyond the destructiveHint=true annotation by disclosing there is no undo, that the file is saved on success, the document-module restriction, and the Excel refusal when a shape-call check cannot be performed. These are exactly the behavioral traits an agent needs before a destructive write.

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 safety or precondition information, with the destructive nature front-loaded. No filler or repetition of the title.

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 destructive, 5-parameter tool with an output schema already covering returns, the description supplies the safety posture, the alternative (read first), the exclusions, and the failure condition. Nothing material is missing.

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 coverage is 100%, so the schema already documents all five parameters, including the rationale for allow_protected, allow_invalidate_signature, and expected_content_token. The description only indirectly reinforces the content-token idea ('stale look') and does not add syntax or format detail, 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 resource ('Permanently deletes a VBA module from an Office file and saves it'), plus the permanence qualifier. An agent can instantly distinguish it from xlide_write_module, xlide_edit_module, and xlide_rename_module.

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?

Explicit when-to-use and prerequisites: ask the user first, read the module before deleting so it can be restored, and note that document modules cannot be deleted. It effectively routes the agent to xlide_read_module before this call.

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