Skip to main content
Glama

ie_frames

List the frames and iframes of the current page with index, name, id and src, so you can target each one by index or name in other tools' frame argument.

Instructions

List the frames/iframes of the current page (index, name, id, src). Use the index or name with the 'frame' arg of other tools.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "ie_frames"
  }
}

Input Schema

NameRequiredDescriptionDefault
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.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

A3.8/5.0
Behavior3/5

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

No annotations exist, so the description carries full behavioral burden. It does disclose scope ('current page') and the exact returned fields, implying a read-only enumeration, but says nothing about failure modes, ordering, or whether frame listing behaves differently over COM versus a tab target despite the schema flagging COM limitations for other tools.

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 output shape, followed immediately by the actionable next step. No filler whatsoever.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple read tool with no output schema, the description compensates by enumerating the returned fields and explaining the follow-up usage. Minor remaining gaps are edge cases (empty frame list, COM-mode frame availability), which are not essential for correct invocation.

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

Parameters3/5

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

Only one optional parameter exists and schema description coverage is 100%, so the schema already fully documents 'target', including COM and tab semantics. The description adds only the implicit notion that listing applies to the current page; baseline 3 applies.

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 ('List the frames/iframes of the current page') and even names the fields returned (index, name, id, src). It doesn't explicitly contrast with siblings, but no sibling competes for frame enumeration, so the 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 Guidelines4/5

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

It gives clear follow-up guidance: 'Use the index or name with the frame arg of other tools,' which tells the agent what to do with the result. It lacks a when-not or preconditions statement (e.g., no frames on page, COM-mode restrictions), but the intended context is clear.

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