Skip to main content
Glama
Sign In
Hangeul-mcp

Hangeul-mcp

by pblsketch
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

set_columns

Set the number of columns in a HWP/HWPX document body and save the result to a new file.

Instructions

Set the body column count and write a NEW file (delegate).

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>",
      "out_path": "<out_path>"
    },
    "name": "set_columns"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathYes
out_pathYes
col_countNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.2.1

TDQS

C2.4/5.0
Behavior2/5

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

No annotations provided, so the description must cover behavior. It mentions writing a NEW file but does not state whether the original is modified, if file overwriting occurs, or any safety considerations. Minimal behavioral disclosure.

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?

Very concise single sentence, but underspecified. It is front-loaded but does not contain enough information to be fully effective.

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

Completeness1/5

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

With 3 parameters, no annotations, and no schema descriptions, the description is far from complete. No mention of file types, return values, or what 'delegate' means. An output schema exists but is not provided here, so cannot compensate.

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 description coverage is 0%, so the description must explain parameters. It only hints at col_count. The required parameters 'path' and 'out_path' are not described at all. No explanation of what they represent (input file? output location?).

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

Purpose4/5

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

The description states clearly that the tool sets body column count and writes a new file. It distinguishes from sibling tools that deal with headers, footers, margins, etc. The term '(delegate)' is unclear but does not obscure the main purpose.

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 like set_page_size or set_header. Implied usage from name and description, but no explicit conditions or exclusions.

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