Skip to main content
Glama
Sign In
ie-mcp

ie-mcp

by thomfilg
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

ie_press_key

Press a key (Enter, Tab, Escape, etc.) on an element or active element in legacy IE web applications. Supports literal characters and navigation keys.

Instructions

Press a key on an element (if by/value given) or the active element. Key names: Enter, Tab, Escape, Space, Backspace, Delete, Up/Down/Left/Right, Home, End, PageUp, PageDown, F5 — or a literal character.

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": {
      "key": "<key>"
    },
    "name": "ie_press_key"
  }
}

Input Schema

NameRequiredDescriptionDefault
byNo
keyYes
waitNo
frameNo
valueNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior3/5

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

With no annotations, the description carries the burden. It covers basic behavior: key names and element targeting. However, it does not disclose behavior for parameters like 'wait', 'frame', or 'by'/'value' selectors. The tool's side effects (e.g., triggering events) are implied but not stated.

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 a single sentence followed by key name examples. Every word is necessary, and the structure is efficient. No fluff.

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?

Given 5 parameters and no schema descriptions, the description is only partially complete. It explains the core function and key naming but omits details on element targeting, waiting, and frame handling. For a 'press key' tool, it is adequate for basic use but lacks full coverage.

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 0%. The description only explains the 'key' parameter by listing valid key names. It fails to explain 'by', 'value', 'wait', and 'frame', which are critical for correct usage. This leaves the agent guessing about element targeting and timing.

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?

The description clearly states 'Press a key on an element' and distinguishes between targeting a specific element (if by/value given) or the active element. It also lists valid key names, making the tool's purpose explicit. This differentiates it from sibling tools like ie_click or ie_fill.

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 implies usage scenarios: when you need to press a key on an element or the active element. It does not explicitly state when not to use it or name alternatives, but the context is clear enough for an AI agent to infer appropriate use cases.

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