Skip to main content
Glama

ie_fill

Types text into input or textarea elements with automatic waiting, and fills legacy IE windows or tabs via COM by setting values with script and firing synthetic events.

Instructions

Type text into an input/textarea element (auto-waits). Over COM (target hwnd:/tab:) the value is set by script and key/change/blur events are fired: synthetic, not keystrokes.

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": {
      "by": "<by>",
      "value": "<value>",
      "text": "<text>"
    },
    "name": "ie_fill"
  }
}

Input Schema

NameRequiredDescriptionDefault
byYes
textYes
clearNo
frameNo
valueYes
targetNoWhere to act: omit it for the session's IE driver; hwnd:<n> acts over COM on the window <n> (a modal dialog's hwnd from a NOTICE or ie_windows), tab:<n> on an attached tab. Over COM, DOM access is script, input is synthetic (script events and a timer click, not mouse or keyboard input; keys are posted window messages) and only id, name, tag, class, link_text and (documentMode 8+) css locators work.
timeoutNoseconds to wait for the element (default 10)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

B3.2/5.0
Behavior3/5

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

With no annotations at all, the description carries the full burden, and it does make one genuinely valuable disclosure: over COM, the value is set by script and key/change/blur events are synthetic rather than real keystrokes, which matters for frameworks that gate on trusted input. It also notes the auto-wait. It says nothing about failure behavior, whether existing content is replaced or appended, or what a timeout produces.

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

Conciseness4/5

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

Two sentences, front-loaded with the action and the auto-wait, then the COM caveat. Nothing is padding. The second sentence is dense but every clause (script-set value, fired events, not keystrokes) changes how an agent should interpret the result.

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 7-parameter fill tool with no annotations and no output schema, the definition covers the action and the most surprising execution mode but leaves several parameters undescribed and says nothing about results or error conditions. It is workable for the common session-driver case but thin for the COM path it goes out of its way to mention.

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 only 29%, so the description needs to compensate, and it largely does not. It never explains `by` (locator strategy), `clear`, `frame`, or `text` vs `value`, and it leaves `timeout` meaning implicit through "auto-waits". The only locator detail, that only id/name/tag/class/link_text/css work over COM, appears in the schema's own `target` description rather than the tool description.

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 opens with a specific verb and resource: "Type text into an input/textarea element (auto-waits)." That is enough to separate it from siblings like ie_click, ie_select or ie_press_key. It could be stronger if it explicitly distinguished itself from ie_js-based text injection, but the core purpose 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?

Usage is only implied by the resource type: use it when you need to populate a form field. There is no explicit when-to-use, when-not-to-use, or named alternative for cases such as needing real keystrokes (ie_press_key) or running arbitrary script (ie_js). The COM-vs-driver distinction is stated, but as a behavioral caveat rather than routing guidance.

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