Skip to main content
Glama
Sign In
Hangeul-mcp

Hangeul-mcp

by pblsketch
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

hwpx_to_html

Converts HWPX files to HTML format, enabling access to Korean word processor content in web browsers.

Instructions

Convert HWPX to HTML via python-hwpx (delegate extra required).

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "path": "<path>"
    },
    "name": "hwpx_to_html"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.2.1

TDQS

C2.8/5.0
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations provided; description only mentions the method (python-hwpx) but omits behavioral traits like formatting preservation, limitations, or error handling.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Single concise sentence front-loads the core information; however, it is slightly too brief missing some context that could be added without verbosity.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Description lacks essential details about input constraints, output format, error scenarios, and prerequisites beyond a vague mention of delegate extra. The presence of an output schema is noted but not exploited.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema has one parameter 'path' with no description; tool description adds no additional meaning to the parameter, leaving its semantics undefined.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Description clearly states the action (convert) and resources (HWPX to HTML), and notes the use of python-hwpx delegation. This distinguishes it from sibling tools like hwpx_to_markdown.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Only minimal guidance is given via 'delegate extra required', implying a prerequisite but no explicit comparison to alternatives or when to use this tool versus similar ones.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools