Skip to main content
Glama
Sign In
Hangeul-mcp

Hangeul-mcp

by pblsketch
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

merge_table_cells

Merge a specified cell range in an HWP table and write the modified document to a new file.

Instructions

Merge a table cell range (e.g. A1:B2) 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>",
      "table_index": "<table_index>",
      "cell_range": "<cell_range>",
      "out_path": "<out_path>"
    },
    "name": "merge_table_cells"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathYes
out_pathYes
cell_rangeYes
table_indexYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.2.1

TDQS

B3.1/5.0
Behavior2/5

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

No annotations are provided, so the description must carry the full burden. It only mentions 'delegate' and creating a new file, but does not disclose side effects (e.g., whether the original file is modified), error conditions, or required permissions.

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

Conciseness5/5

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

A single sentence with no filler, front-loaded with the core action. Every word earns its place, and the parenthetical '(delegate)' adds key context without extra verbiage.

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?

Despite having an output schema (not shown), the description omits critical context: whether the merge overwrites if 'out_path' exists, whether the original file is unchanged, and what 'delegate' entails. For a tool with 4 required params and a potentially destructive operation, this is insufficient.

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 description coverage is 0%, so the description must compensate. It only gives an example for 'cell_range' (A1:B2) and mentions 'path' and 'out_path' implicitly, but does not explain 'table_index' or the meaning of 'delegate'. The schema itself provides no parameter descriptions.

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 action ('merge a table cell range') and the output ('write a NEW file'), providing a specific verb and resource. It stands out from siblings like 'split_merged_cell' by emphasizing the file creation aspect.

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. Siblings like 'set_cell_shading' or 'split_merged_cell' exist, but the description does not explain when merging is appropriate or mention any prerequisites.

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