No user-submitted related servers found.
Scored across 7 tools
The core pipeline (get_writing_guide → draft_press_structure/check_structure → build_document) is clearly differentiated, but get_writing_guide, get_rules, and list_ministries all return per-ministry/per-doc-type configuration information and their boundaries (writing rules vs. formatting values vs. availability table) require reading careful descriptions. build_from_structure is explicitly documented as an alias of build_document, giving two names for identical behavior.
All names follow a verb_object snake_case pattern (get_*, list_*, check_*, draft_*, build_*), which is predictable and readable. Minor deviation: build_document names an action+object while build_from_structure names an action+source, so the two siblings don't distinguish themselves through naming alone.
Seven tools is well within a healthy scope for a document-generation server with a discover→validate→build workflow. The only bloat is build_from_structure, a pure duplicate of build_document that adds no capability.
The generation lifecycle is well covered: discover supported ministries, fetch formatting rules, fetch writing guidance, draft a press structure from facts, validate, build HWPX, and optionally export Markdown. Gaps are minor — there is no tool to read/parse an existing HWPX or to inspect/regenerate a previously built file, so agents cannot round-trip an existing document.