Skip to main content
Glama

ie_select

Select an option in a dropdown by visible label, value attribute, or zero-based index, with configurable timeout and post-selection wait for reliable automation.

Instructions

Select an in a dropdown, by label (visible text), option_value, or index. Provide exactly one of label/option_value/index.

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

Input Schema

NameRequiredDescriptionDefault
byYes
waitNoseconds to pause after selecting (default 2)
frameNo
indexNooption index (0-based)
labelNooption visible text
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)
option_valueNooption value attribute

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

B3.4/5.0
Behavior2/5

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

With no annotations, the description carries the full behavioral burden and does not disclose what happens when the option is absent, whether change/input events are fired, or whether the call fails or silently no-ops on timeout. The rich 'target' semantics (session driver vs hwnd COM vs tab) live only in the schema, so the prose adds little beyond the selection mechanism itself.

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?

Two short sentences, front-loaded with the action and the mechanism, with the mutual-exclusivity constraint last. No filler or redundancy.

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 9-parameter tool with no annotations and no output schema, the description is thin: error/timeout outcomes and event side effects are unstated, and the tension between required 'by'/'value' and 'provide exactly one of label/option_value/index' is left for the agent to reconcile. It is adequate to make a correct call in the common case but leaves meaningful gaps.

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?

The schema leaves the two required parameters ('by' and 'value') undocumented, and the description partially compensates by explaining that the selection key is one of label/option_value/index and must be supplied exclusively. It still does not state the literal string values 'by' accepts, so the mapping from 'by' to those keys remains an inference.

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 names a specific verb and resource (select an <option> inside a <select> dropdown) and enumerates the three selection keys, which distinguishes it from ie_click, ie_fill, and ie_js without naming them. It stops short of explicitly contrasting with those siblings, so a 5 is not warranted.

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 line 'Provide exactly one of label/option_value/index' gives a real usage constraint for choosing among the three selector modes. However, there is no guidance on when to prefer this tool over ie_click or ie_js on a custom dropdown, and no mention of prerequisites such as the element being in the current frame/document.

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