Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault

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

CapabilityDetails
tools
{
  "listChanged": true
}
logging
{}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}
extensions
{
  "io.modelcontextprotocol/ui": {}
}
experimental
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
convert_md_to_hwpxA

Convert a Markdown file to HWPX format.

Use this when the user wants to create an HWPX document from a Markdown file WITHOUT providing a reference HWPX template. Generates a complete document with cover page, page headers/footers, heading auto-numbering, native tables, code blocks, lists, and blockquotes.

analyze_hwpxA

Analyze an existing HWPX file and return its full structure.

Outputs font definitions, border/fill styles, character styles (charPr), paragraph styles (paraPr), page/margin settings, and the complete body structure including all paragraphs and tables with cell details.

Use this as the first step when the user provides a reference HWPX file for replication or editing.

build_hwpxA

Build an HWPX file from a template and optional XML overrides.

Workflow:

  1. Start from the base template skeleton.

  2. Optionally overlay a document-type template (gonmun/report/minutes).

  3. Optionally override header.xml (styles) and/or section0.xml (body).

  4. Pack as a valid HWPX archive and validate.

When a user provides a reference HWPX, first call analyze_hwpx() and extract_hwpx_xml() to get the header/section XML, then write a new section0.xml with only the required text changes, and pass it here.

extract_hwpx_xmlA

Extract header.xml and section0.xml from an HWPX file.

Use this to get the raw XML from a reference HWPX so you can:

  • Read the exact charPrIDRef/paraPrIDRef/borderFillIDRef values in use

  • Copy the header.xml for reuse in build_hwpx()

  • Edit section0.xml text nodes and pass the modified file to build_hwpx()

validate_hwpxA

Validate the structural integrity of an HWPX file.

Checks: valid ZIP, required files, mimetype content/position/compression, and XML well-formedness.

page_guard_hwpxA

Check that output HWPX has not drifted in page count vs a reference.

Best for SAME-STRUCTURE edits (filling values into a form, replacing text in-place without adding/removing paragraphs or tables). When sections are added, removed, or restructured, expected differences will be reported as failures — in that case use validate_hwpx for integrity checks instead.

Compares paragraph count, table count, table dimensions, explicit page/column breaks, and overall text length between reference and output.

extract_text_hwpxB

Extract plain text content from an HWPX file.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A3.9/5.0

Scored across 7 tools

Disambiguation5/5

Each tool targets a distinct operation: validation, conversion from Markdown, structure analysis, template-based building, raw XML extraction, page-count verification, and plain text extraction. No two tools have overlapping purposes, and the descriptions clearly differentiate them.

Naming Consistency3/5

Most tools follow a verb_hwpx pattern (validate_hwpx, analyze_hwpx, build_hwpx), but convert_md_to_hwpx and extract_hwpx_xml deviate. The extract_hwpx_xml and extract_text_hwpx tools especially have inconsistent ordering of source/object (hwpx before xml vs. after text). While all names start with a verb, the overall pattern is not uniform.

Tool Count5/5

With 7 tools covering creation, analysis, extraction, validation, and page-count verification, the count is well-scoped for an HWPX manipulation server. Each tool earns its place without redundancy or bloat.

Completeness5/5

The tool set provides full lifecycle coverage: create (convert_md_to_hwpx, build_hwpx), read/analyze (analyze_hwpx, extract_hwpx_xml, extract_text_hwpx), and verify (validate_hwpx, page_guard_hwpx). Editing is achievable via the build_hwpx workflow with extracted XML, leaving no obvious gaps.

Maintenance

ActivityInactive
ResponsivenessNo issues