Skip to main content
Glama
Sign In
windows2-mcp

windows2-mcp

by verisoft-ai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

switch_to_frame

Focus automation on a specific frame or iframe inside an Internet Explorer window using its index, name, or element ID — only after targeting the IE window itself.

Instructions

Switch context into an iframe or frame inside an IE window. After switching, element finds are scoped to that frame's document. Provide exactly one of: index (0-based integer), name (frame name/id attribute), or elementId (element ID of the iframe element). Only supported in IE context (after switch_to_window targeting an IE window).

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": "switch_to_frame"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNoFrame name or id attribute
indexNo0-based frame index
elementIdNoElement ID of an <iframe> or <frame> element (from find_element)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4/5.0
Behavior4/5

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

With no annotations provided, the description carries full burden of behavioral disclosure. It clearly explains the scoping effect ('element finds are scoped to that frame's document') and the prerequisite (IE context), which is good transparency for a context-switching 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 description is three sentences, each adding unique value: what the tool does, the scoping effect, and usage constraints. No waste and front-loaded with the primary function.

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?

Given the low complexity (3 optional params, no output schema, no nested objects), the description covers purpose, scoping, and constraints well. It could mention that after using this tool, switch_to_default_content or switch_to_parent_frame can go back, but this is a minor gap.

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?

Schema description coverage is 100%, so each parameter already has a basic description (e.g., 'Frame name or id attribute'). The tool description adds context about using exactly one parameter and the IE-specific constraint, but does not add deeper semantic value beyond what the schema provides.

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 clearly states the tool switches context into an iframe or frame inside an IE window, and that subsequent element finds are scoped to that frame. This verb-resource pair is specific and distinguishes it from siblings like switch_to_parent_frame and switch_to_window.

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?

The description explicitly states the tool is only supported in IE context after switch_to_window, and requires exactly one of three parameters. It does not mention when not to use it or alternatives like switch_to_default_content, but the context is clear enough.

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

Deploy Server

Other Tools