Skip to main content
Glama
mjyoo2
by mjyoo2

hwp_form_param_action

Apply property changes to HWP form controls (checkboxes, combo boxes, dates, text areas) by executing an action with a specified parameter set, enabling precise control over document fields.

Instructions

Execute HWP action with form control HParameterSet.

Supported param_set_name values and their key properties:

  • HFormCheckBox: Name, Checked (bool), GroupName, Value, EnabledField (bool), ReadOnly (bool)

  • HFormComboBox: Name, Items (list of strings), SelectedIndex, Editable (bool), ListRows

  • HFormDate: Name, DateFormat, DefaultDate, MinDate, MaxDate

  • HFormDropDown: Name, Items (list of strings), SelectedIndex, Width

  • HFormEdit: Name, Text, MaxLength, PasswordChar, MultiLine (bool), ReadOnly (bool), InputMask

  • HFormListBox: Name, Items (list), SelectedIndex, MultiSelect (bool), ListRows, Width, Height

  • HFormNumber: Name, Value, MinValue, MaxValue, DecimalPlaces, SpinButton (bool)

  • HFormOLE: Name, CLSID, Width, Height, ProgID, DisplayAsIcon (bool)

  • HFormPopupButton: Name, Caption, Width, Height, Action

  • HFormPushButton: Name, Caption, Width, Height, OnClick (script)

  • HFormRadioButton: Name, GroupName, Checked (bool), Value, Label

  • HFormScrollBar: Name, Min, Max, Value, SmallChange, LargeChange, Orientation (0=horizontal, 1=vertical)

  • HFormTextArea: Name, Text, Rows, Cols, MaxLength, ReadOnly (bool), ScrollBars (0=none, 1=horizontal, 2=vertical, 3=both)

Args: doc_id: Document ID from open_document action_name: HWP action to execute param_set_name: Must be one of the form param sets listed above params: Properties to set on the param set

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
doc_idYes
paramsNo
action_nameYes
param_set_nameYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior2/5

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

No annotations are present, so the description carries the full burden of disclosing side effects. It only states that it executes an action and sets properties; it does not say whether this mutates the document, whether actions like HFormPushButton.OnClick can trigger scripts, or what result to expect. This is a significant transparency gap for an 'execute action' tool.

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?

The purpose is front-loaded, and the long block of form-control variants is formatted as scannable bullets where each line adds distinct property information. There is no filler or repetition.

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?

For a high-variance tool with a bare schema, the parameter table is a strong contribution and the output schema covers return shape. But the description omits action_name semantics, side effects, and any usage exclusions, so an agent still has to guess at some call requirements.

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

Parameters4/5

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

With 0% schema coverage, the description compensates by listing every supported param_set_name and the relevant properties/types, and it clarifies doc_id comes from open_document. It falls short only on action_name, which is left as 'HWP action to execute' with no indication of valid values or how it interacts with each form control.

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 opening sentence names a specific verb ('Execute') and resource ('HWP action with form control HParameterSet'), and the enumerated HForm* param sets ground the tool in form controls, distinguishing it from siblings like hwp_table_param_action or run_hwp_action. The scope is unambiguous.

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

Usage Guidelines3/5

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

The description makes clear the tool operates on form-control param sets, so when an agent is dealing with HFormCheckBox/HFormEdit etc., this tool is implied. However, it never explicitly states when to choose this over alternatives (set_form_properties, get_form_data, run_hwp_action) or when not to use it, leaving exclusion criteria to inference.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/mjyoo2/hwp-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server