Skip to main content
Glama
Sign In
Hangeul-mcp

Hangeul-mcp

by pblsketch
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

set_cell_shading

Define a fill color for a specific table cell and save the modified HWP/HWPX document as a new file.

Instructions

Set a table cell fill color 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>",
      "row": "<row>",
      "col": "<col>",
      "fill_color": "<fill_color>",
      "out_path": "<out_path>"
    },
    "name": "set_cell_shading"
  }
}

Input Schema

NameRequiredDescriptionDefault
colYes
rowYes
pathYes
out_pathYes
fill_colorYes
table_indexYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.2.1

TDQS

C2.8/5.0
Behavior3/5

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

Without annotations, the description must disclose behaviors. It correctly notes that a new file is created (non-destructive to original), but omits details on side effects, permissions, or what happens to the original file.

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?

The description is very concise (one sentence), which is good, but the term 'delegate' is jargon and unclear. It could be more helpful while staying succinct.

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?

Given 6 required parameters and no schema descriptions, the description is insufficient. It does not explain output schema, color format, or cell identification, leaving many gaps for the agent.

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%. The description hints at some parameters (cell, color, file output) but does not explicitly map to the 6 required parameters or explain their formats.

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 clearly identifies the action (set fill color) and resource (table cell), and notes that it produces a new file. However, it does not distinguish this tool from siblings like 'set_columns' or 'merge_table_cells'.

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. The term 'delegate' is ambiguous and does not clarify context of use.

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