ooxml-integrity
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
Checks .docx and .pptx files on this machine for structural defects and for review content an edit lost: comments, tracked changes, notes, headers. After editing a document, call compare with the original as source and your output as edited, and fix or report what it finds before returning the file. If the user asked for a change that removes something, such as accepting a tracked change, declare it in expect. Use check when there is no original. The verdict says 'clean' only when nothing was found and every surface was checked; 'no findings in checked surfaces' means part of the file was not assessed, listed under coverage.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| checkA | Self-check one .docx or .pptx: comment anchors, footnotes, styles, numbering, relationships and tracked-change markup in a document; text that overflows its box and shapes off the slide in a deck. Same as |
| compareA | Everything check does on the edited file, plus what the edit lost relative to the original: comments, tracked insertions and deletions, footnotes and endnotes, headers and footers, text. Same as |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 2 tools
The two tools have clearly distinct purposes: `check` audits a single file in isolation, while `compare` adds differential analysis against an original. The descriptions explicitly state when to use each (use compare when the original is available; check otherwise) and even cross-reference each other, leaving no real ambiguity.
Both names are single imperative verbs in the same style (`check`, `compare`), forming a clean, predictable pair. There is no mixing of conventions, camelCase, or noun/verb inconsistency.
Two tools is on the thin side for the surface, though the server's scope is narrow (integrity auditing of OOXML files). The pair covers the core mode split, but a smaller-than-typical set leaves little room for adjacent operations like batch checking or repair.
The lifecycle of an integrity audit is covered: standalone checking plus comparison against an original, with expectations handling intentional removals and PPTX limitations documented. Minor gaps exist—no batch/multi-file operation and no remediation or report-export tool—but agents can work around them by invoking the CLI per file.