Skip to main content
Glama

ie_get

Read an element's text, value, or named attribute/property from legacy IE-mode pages. Use locators and optional frame, target, or timeout settings to retrieve the needed content.

Instructions

Read an element's text (default), its 'value', or a named attribute/property. Set attr=text|value|.

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_get"
  }
}

Input Schema

NameRequiredDescriptionDefault
byYes
attrNotext (default) | value | any attribute name
frameNo
limitNo
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

C2.9/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden, and it discloses almost nothing: it does not say what happens when the element is not found, whether the call blocks until the timeout, whether it returns null versus raising, or whether it triggers any side effects. The one behavioral detail present ('text' is the default) is a parameter default, not deeper transparency about the read operation itself.

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 short, front-loaded sentences with no filler: the default behavior comes first and the override syntax second. Slightly more framing would help, but nothing is wasted.

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?

With seven parameters at 43% description coverage, no output schema, and no annotations, this definition leaves too much unstated for the calling agent. A read tool needs to say what it returns (string, null, attribute value type) and how failures surface; instead the description covers only the attr selector.

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 43%, so the description must compensate, and it barely does — it only restates the attr values already documented in the schema. The required parameters 'by' and 'value' carry no explanation in either schema or description, leaving the agent to guess that 'by' is a locator type and 'value' its operand; frame and limit are likewise silent.

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 states a specific verb and resource ('Read an element's text') and enumerates the three readable outputs (text default, value, named attribute), which is enough to separate it from mutating siblings like ie_fill or ie_click. It stops short of explicitly naming a sibling or covering cases such as frames or HTML extraction, so it is clear but not fully differentiated.

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 only guidance is the default/override behavior for attr ('text (default) | value | <attribute name>'). There is no statement of when to prefer ie_get over ie_html, ie_js, or ie_grid, and no preconditions such as needing an attached session or an element being present. Usage is implied rather than directed.

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