Skip to main content
Glama
Sign In
Hangeul-mcp

Hangeul-mcp

by pblsketch
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

validate_hwpx

Checks HWPX documents for correct zip structure, mimetype, and XML declarations to ensure file integrity.

Instructions

Validate HWPX package integrity (zip layout, mimetype, XML declarations); ok mirrors valid.

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": "validate_hwpx"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.2.1

TDQS

C2.9/5.0
Behavior2/5

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

No annotations provided, so description bears full burden. It mentions checking integrity but does not disclose error handling, side effects, or return behavior beyond cryptic 'ok mirrors valid'. Read/write nature is implicit.

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

Conciseness3/5

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

Two sentences, concise. However, 'ok mirrors valid' is unclear jargon that may confuse agents. Could be restructured for clarity.

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

Completeness3/5

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

With an output schema, return values need not be described. The tool has one parameter and no annotations; description is minimal but covers the core action. Lacks detail on integrity definition and output format.

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

Parameters2/5

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

Schema coverage is 0% meaning no parameter descriptions. The tool description does not explain what 'path' refers to (e.g., file system path, HWPX file). The only parameter is minimally documented.

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?

The description clearly states the verb 'Validate' and the resource 'HWPX package integrity', specifying sub-checks (zip layout, mimetype, XML declarations). It distinguishes itself from sibling tools, none of which perform validation.

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?

No guidance on when to use this tool versus alternatives. Does not mention prerequisites, typical use cases, or what to do if validation fails.

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