Skip to main content
Glama
Sign In
ie-mcp

ie-mcp

by thomfilg
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

ie_dialog

Accept, dismiss, retrieve text, or send keystrokes to JavaScript dialogs (alert/confirm/prompt) in IE-mode web applications.

Instructions

Handle a JS dialog (alert/confirm/prompt). action: accept (default) | dismiss | text | sendkeys (with text). Note: OS-level IE modals may be unreachable.

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

Input Schema

NameRequiredDescriptionDefault
textNotext for sendkeys
actionNoaccept | dismiss | text | sendkeys

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.5/5.0
Behavior4/5

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

Discloses possible actions (accept, dismiss, text, sendkeys) and warns that OS modals may be unreachable. Lacks detail on error cases (e.g., non-existent dialog), but covers key behavior.

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 concise sentences: first states purpose and actions, second adds important limitation. No redundancy.

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?

Adequate for a simple tool: covers purpose, actions, limitation. Minor omission: no mention of return value for 'text' action, but acceptable without output schema.

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

Parameters5/5

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

Schema has 100% coverage, but description adds significant value: clarifies valid action values, notes default (accept), and explains text parameter usage for sendkeys.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Clearly states it handles JS dialogs (alert/confirm/prompt) and lists specific actions. Distinct from sibling tools, which focus on navigation, clicks, etc.

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?

Provides context for use: when a dialog appears. Mentions limitation about OS-level modals. No explicit alternatives, but no sibling tool targets dialogs.

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