Skip to main content
Glama
Sign In
ie-mcp

ie-mcp

by thomfilg
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

ie_sleep

Pause automation for a specified number of seconds as a fallback when standard wait conditions are not applicable in legacy IE web application testing.

Instructions

Sleep for N seconds (last resort; prefer ie_wait_ready / ie_wait_text).

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

Input Schema

NameRequiredDescriptionDefault
secondsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.7/5.0
Behavior4/5

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

No annotations exist, but the description accurately describes the simple blocking sleep behavior. Could mention potential effects on automation flow, but given the trivial action, it's largely sufficient.

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?

Extremely concise with a single meaningful sentence plus parenthetical guidance. No wasted words.

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

Completeness5/5

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

Complete for a simple sleep tool with no output schema. The brief description covers purpose, usage, and alternatives.

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?

The sole parameter 'seconds' is explained by 'sleep for N seconds', compensating for the schema's lack of description. No further details needed.

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 the tool sleeps for N seconds and distinguishes itself from siblings by suggesting ie_wait_ready/ie_wait_text as preferred alternatives.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

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

Explicitly marks itself as a last resort and names two preferable alternatives, providing clear when-to-use guidance.

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