Skip to main content
Glama
Sign In
windows2-mcp

windows2-mcp

by verisoft-ai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

close_window

Destructive

Close a window element by providing its element ID using the UIA Window pattern.

Instructions

Close a window element via the UIA Window pattern.

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": {
      "elementId": "<elementId>"
    },
    "name": "close_window"
  }
}

Input Schema

NameRequiredDescriptionDefault
elementIdYesElement ID returned by find_element or get_window_element

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.5/5.0
Behavior3/5

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

The annotation 'destructiveHint: true' already signals a destructive operation. The description adds that it uses the UIA Window pattern, but does not elaborate on behavioral traits (e.g., whether the element becomes invalid, if the window handle is removed, or any side effects). With the annotation, the baseline is met but little extra value is added.

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 of 10 words, front-loading the key action and resource. Every word contributes; there is no fluff. It is appropriately sized for a simple, single-purpose tool.

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 low complexity (one parameter, no output schema, annotations present), the description is adequate but lacks depth. It does not explain what 'UIA Window pattern' implies or how the tool differs from similar window-closing operations. The agent may need additional context to use it correctly in all scenarios.

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 description coverage is 100%, and the schema already describes the 'elementId' parameter meaningfully. The tool description does not add any additional semantic context beyond what the schema provides. Baseline score 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 ('close') and the resource ('window element via the UIA Window pattern'). It is specific and distinguishes 'close_window' from siblings like 'click_element' or 'invoke_element' which have different effects.

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

Usage Guidelines2/5

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

No guidance is provided on when to use this tool versus alternatives. For example, it does not explain why one would choose 'close_window' over clicking a close button via 'click_element' or using 'invoke_element'. The agent is left to infer usage context.

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