md-to-word
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.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| compile_markdownC | Compile Markdown into a Word (.docx) document. Ensure structures beyond standard Markdown (e.g. captions, TOC, page breaks, abstract, math blocks) follow the contract in get_guide. Uses the provided format file, or defaults to a built-in preset. |
| validate_manuscriptB | Validate a Markdown manuscript's syntax and non-standard Markdown structure mappings against the compilation contract before export. |
| get_guideA | Read this before drafting or compiling. Explains requirements confirmation, non-standard Markdown structure mappings, and the compilation contract. |
| get_manualB | Read the full manual when a spelling or behaviour is not certain: every style name, YAML key, equation rule, CSL preset and known limit, plus §9 for custom covers, front matter, section/page numbering, and |
| extract_format_from_docxB | Read a reference .docx template (institution, journal, or organization) and produce a draft format file. The draft lists every value it could determine and a 'to confirm' list it could not; review those before compiling. |
| list_presetsA | List all available built-in style presets (Simplified/Traditional Chinese Academic, Tech Report, Nature English Paper) with typography specifications. |
| inspect_presetC | Inspect the full format.txt typography specification for a given preset. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| draft_academic_manuscript | Guide the LLM to draft a structured Markdown manuscript compatible with md-to-word. Args: topic: The subject or title of the paper/report to write. preset: Target style preset ('zh-academic', 'zh-tw-academic', 'zh-report', or 'en-nature'). lang: Language for the manuscript ('zh' or 'en'). |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| get_contract_guide | Access the packaged workflow guide (same text as SKILL.md). |
TDQS
Scored across 7 tools
Most tools have clearly distinct roles: validate_manuscript checks syntax, compile_markdown produces the document, extract_format_from_docx derives formats, and list_presets/inspect_preset form a clear list-vs-detail pair. The one real overlap is get_guide versus get_manual, both being 'read the documentation' tools differentiated only by short-vs-full scope, which risks misselection.
Every tool follows a consistent snake_case verb_noun pattern (get_guide, list_presets, inspect_preset, validate_manuscript, compile_markdown, extract_format_from_docx). The verbs are used predictably: get_ for reading docs, list_/inspect_ for presets, validate_/compile_/extract_ for operations.
Seven tools is well-scoped for a Markdown-to-Word pipeline: two documentation readers, one validator, two preset tools, one format extractor, and one compiler. Each tool maps to a distinct step in the workflow and none appears redundant.
The lifecycle is largely covered: learn the contract (get_guide/get_manual), inspect presets, derive a format from a reference docx, validate, then compile. The gap is format authoring — extract_format_from_docx produces a draft with 'to confirm' items, but there is no tool to validate or finalize a format file, and the custom cover/front-matter features described in §9 have no direct tool support, requiring manual file editing.