Extract structural facts from a .docx file: heading hierarchy, TOC consistency, header/footer consistency, page-numbering-field presence, orphaned/empty styles, list-numbering restarts, and image/table caption presence + sequencing. Returns facts and anomaly flags only — never a verdict on correctness (see the server's global instructions).

Accepts the document either as a filesystem path OR as inline content_base64 (with filename required alongside it) — useful when the .docx only exists in the conversation (e.g. a file uploaded directly in chat) rather than saved to disk. Exactly one of the two input forms must be given.

Per-paragraph resolved font/size/weight (full style-chain resolved, with provenance per property) plus flags for paragraphs whose resolved combination is statistically unique in the document, and for paragraphs whose runs don't all resolve to the same combination. Facts and anomaly flags only — never a verdict on what formatting should be (see the server's global instructions).

Accepts the document either as a filesystem path OR as inline content_base64 (with filename required alongside it) — for a .docx that only exists in the conversation rather than saved to disk. Exactly one of the two input forms must be given.

Tokenizes the filename (stripping extension, separators, common document-type stopwords, and — heuristically — the document owner's own leading First/Last name tokens), then flags any remaining proper-noun-like token that doesn't appear anywhere in the extracted document text. Facts only: presence or absence — never a verdict on whether a mismatch is intentional (brief §3, §4.4).

Accepts the document either as a filesystem path OR as inline content_base64 (with filename required alongside it — this is exactly the name that gets tokenized, so pass the file's real name here, not a placeholder). Exactly one of the two input forms must be given.

Grammar/spelling/punctuation/style findings via a local LanguageTool instance, with paragraph/offset anchors so the model can locate and fix issues precisely. If lang isn't given and the language can't be auto-detected with confidence, asks the client which language it is (MRTR elicitation) rather than guessing. Facts and LanguageTool's own suggestions only — never a rewritten "corrected" version of the text.

Accepts exactly one of: a filesystem path, raw text, or inline content_base64 (with filename required alongside it) for a .docx/.pdf that only exists in the conversation rather than saved to disk.

Per-character font/size/coordinates, computed baseline spacing, margin/indent consistency, font inventory, declared-vs-embedded font substitution detection, and intra-line horizontal collision flags (tab-stop-overflow signature). Facts and anomaly flags only — never a verdict on correctness (see the server's global instructions).

Accepts the document either as a filesystem path OR as inline content_base64 (with filename required alongside it) — for a .pdf that only exists in the conversation rather than saved to disk. Exactly one of the two input forms must be given.

Runs every applicable check for the document (format auto- detected from the file extension: .docx or .pdf) and returns an aggregated report as a report://{file_id} resource URI, plus an inline summary. profile selects a subset: "full" (default, every applicable check) or "typography_only" (just the format's typography/layout check — check_docx_typography for .docx, check_pdf_layout for .pdf). The full persisted report can be re-read later via the returned URI without re-running analysis (brief §5.1/§5.2). Facts and anomaly flags only, aggregated from each check's own output — never a merged verdict (brief §3, see the server's global instructions).

Accepts the document either as a filesystem path OR as inline content_base64 (with filename required alongside it) — for a file that only exists in the conversation rather than saved to disk. Exactly one of the two input forms must be given.