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

Overview Schema Source Related Servers Discussions Admin

Create, rename or delete a form

xlide_manage_form

DestructiveIdempotent

Create, rename, or delete UserForms and Access forms or reports, saving the designer storage and its code module together in the Office file.

Instructions

Creates a UserForm, or an Access form or report, and saves the file. A form is a designer storage and a code module of the same name, and this writes both, which is why it exists rather than xlide_write_module. Renaming and deleting work on Access designs, where both halves move together; for a UserForm they are refused, because nothing here can move the designer storage and doing half of it loses the form. Add controls afterwards with xlide_edit_form, and write its event procedures with xlide_write_module.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`width`	No	For create. Points for a UserForm, twips for Access.
`action`	Yes	'create', 'rename' or 'delete'.
`design`	No	For create in Access: 'form' or 'report'. Elsewhere, a form.	form
`height`	No	For create.
`caption`	No	For create: the caption it opens with.
`new_name`	No	For rename: the new name.
`file_path`	Yes	Absolute path to the Office file.
`form_name`	Yes	The form or report to act on.
`allow_protected`	No	Permit saving a password-protected VBA project. Set true only after the user agrees.
`allow_invalidate_signature`	No	Permit saving a change that removes the VBA project's digital signature, where applicable. Set true only after the user agrees.

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

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."

First observedv0.1.0Sep 20, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Annotations mark this destructive and non-readonly, and the description adds real context beyond them: it writes both designer storage and the code module, and explains that partial rename/delete would lose the form. It also surfaces the destructive consequence of saving and, via the schema, user-agreement gates for protected/signed projects.

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 purpose, then rationale, then restrictions, then next steps – a logical order with no filler. Sentences are dense and somewhat long, but each carries distinct information, so only minor tightening is possible.

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?

With annotations covering safety, a 100%-covered schema, and an output schema for returns, the description supplies everything else needed: scope, refusal conditions, the two-halves write model, and sibling routing.

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 every parameter (width, design, new_name, allow_protected, etc.) is already documented with units and conditions. The description adds behavioral context around rename/delete but no per-parameter syntax 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 specific verbs and resources ('Creates a UserForm, or an Access form or report, and saves the file') and distinguishes the three actions. It explicitly contrasts itself with sibling tools (xlide_write_module, xlide_edit_form), so an agent can tell it apart without opening schemas.

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 the exact contexts and constraints: rename/delete work only on Access designs where both halves move together, and are refused for UserForms. It routes follow-on work to xlide_edit_form (controls) and xlide_write_module (event procedures), covering when-to-use and when-not.

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

Deploy Server