Skip to main content
Glama
Sign In
ie-mcp

ie-mcp

by thomfilg
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

ie_status

Check the current session state of an IE mode browser, including active status, URL, title, and window handles, to verify automation readiness.

Instructions

Session state as JSON: active/alive, title, url, window_handles, and the interaction mode, session identity/directory, and owned browser PIDs/profile.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior2/5

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

No annotations are provided, so the description must cover behavioral traits. It describes the output but does not mention side effects, safety (read-only nature), rate limits, or whether the tool modifies session state. For a read operation, this is a significant gap.

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?

Single sentence packed with key information. It is concise and front-loaded, though a list format could improve readability.

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 no parameters and no output schema, the description covers the main return fields. It is reasonably complete for a status tool, though some details (e.g., exact structure of JSON) are implied rather than explicit.

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

Parameters4/5

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

No parameters exist, so the description's role is minimal. It effectively describes the output structure, which adds value beyond the empty schema.

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 explicitly states it returns session state as JSON, listing specific fields (active/alive, title, url, window_handles, interaction mode, etc.). This clearly distinguishes it from sibling action-oriented 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 Guidelines3/5

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

The description implies use as a status/check tool but does not explicitly state when to use it versus alternatives. No guidance on when not to use or what prerequisites exist.

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