Skip to main content
Glama
Sign In
windows2-mcp

windows2-mcp

by verisoft-ai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

set_url

Navigate the current Internet Explorer window to a specified URL using direct COM bridge calls, without requiring the window to be in the foreground or using keyboard shortcuts.

Instructions

Navigate the current IE window to a URL. No keyboard shortcuts (Ctrl+L) needed and the window does not need to be in the foreground — this calls IHTMLWindow2.navigate directly through the IE COM bridge. Only supported when the active window is an IE window.

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": {
      "url": "<url>"
    },
    "name": "set_url"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesURL to navigate to

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4.2/5.0
Behavior4/5

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

With no annotations, the description fully handles behavioral disclosure. It reveals the underlying mechanism (IHTMLWindow2.navigate via IE COM bridge) and key behaviors (no keyboard shortcut needed, no foreground requirement). It could improve by mentioning potential outcomes (e.g., success/failure handling, asynchronous behavior), but for a simple navigation the current detail is strong.

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 sentences, each adding unique value. The first sentence is the action statement; the second provides critical usage context. No wasted words.

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?

For a simple one-parameter tool with no output schema, the description covers the key constraint (IE window only) and the behavioral nuance (no foreground needed). It is complete enough for an agent to use correctly. Minor gap: does not describe what happens after navigation (e.g., page load wait).

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 coverage is 100% with one parameter 'url' described as 'URL to navigate to'. The description restates this ('Navigate the current IE window to a URL') but adds no additional detail about format, validation, or protocol requirements. Baseline of 3 is appropriate.

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 action ('Navigate') and the resource ('current IE window to a URL'). It distinguishes from sibling tools like navigate_back and navigate_forward by specifying the target is a URL. The constraint 'Only supported when the active window is an IE window' further clarifies scope.

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 explains when to use this tool: to navigate without needing keyboard shortcuts or the window to be in the foreground. It also states the prerequisite (IE window active). However, it does not explicitly mention when not to use it or provide alternatives, though the context is clear.

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