Touchpoint

Overview Schema Source Related Servers Discussions Admin

minimize_window

Minimize any desktop window to the dock or taskbar by providing its window ID. Use the windows() function to retrieve IDs before minimizing.

Instructions

Minimize a window to the dock/taskbar.

Use windows() to find the window ID first.
To restore a minimized window, use activate_window().

Args:
    window_id: The window ID to minimize.

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": {
      "window_id": "<window_id>"
    },
    "name": "minimize_window"
  }
}

Input Schema

Name	Required	Description	Default
`window_id`	Yes

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Addedv0.3.0Jun 15, 2026

TDQS

A4.7/5.0

Behavior4/5

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

With no annotations, the description carries full burden. It honestly describes the action without contradiction. However, it could add minor behavioral details like 'the window is hidden and appears as an icon in the taskbar'. But for a simple action, it is adequate.

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: two sentences plus a bullet for the parameter. No unnecessary words. Action is front-loaded, and every sentence serves a purpose.

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?

Despite the tool's simplicity, the description covers prerequisites (use windows()), alternative actions (activate_window()), and parameter explanation. An output schema exists (not shown), so return values need not be described. Complete for its context.

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?

Only one parameter (window_id) with 0% schema description coverage. The description adds meaning by stating 'The window ID to minimize', which clarifies usage beyond the schema's mere title 'Window Id'.

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?

Description clearly states action ('Minimize a window to the dock/taskbar') and identifies the specific resource (window). It effectively distinguishes from sibling tools like close_window, activate_window, and fullscreen_window.

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 tells when to use the tool (after finding window ID via windows()) and when not to use it (restoring a minimized window should use activate_window()). Provides clear context for usage.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.