Skip to main content
Glama
Sign In
SapperMCP

SapperMCP

by MasterX1582
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Minimize Window

minimize_window

Minimize or iconify a desktop window by its ID or a title substring to clear screen space without closing it.

Instructions

Minimize (iconify) a window by id or title substring.

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": "minimize_window"
  }
}

Input Schema

NameRequiredDescriptionDefault
titleNo
window_idNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.8/5.0
Behavior2/5

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

With no annotations, the description carries the full behavioral burden and falls short: it does not say how the window is chosen if a title matches multiple windows, which selector wins when both are given, or whether the window can be recovered. Only the core mutation is disclosed.

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?

A single front-loaded sentence with no filler; the selector mechanism is stated in the same breath as the action. Nothing could be removed without losing meaning.

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

Completeness2/5

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

An output schema exists so return values need not be described, but for a mutation tool with zero annotation coverage and zero schema parameter descriptions, the definition leaves too much unspecified. Ambiguity about selector precedence and multi-match behavior is a real risk when calling it.

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

Parameters2/5

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

Schema description coverage is 0%, so the description must compensate, and it only partially does: it clarifies that 'title' is a substring match rather than exact and that 'window_id' is an alternative selector. It omits precedence rules, format of the id, and that both parameters are optional with no stated default target.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb ('minimize') plus the synonym 'iconify' and the target resource ('a window'), so the action is unambiguous. It is distinguishable from siblings like maximize_window, restore_window, and close_window by the verb itself, though no sibling is named.

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?

There is no guidance on when to prefer this tool over restore_window/maximize_window, nor any note on prerequisites or side effects. It also does not say what happens when neither selector is supplied, which matters since both parameters are optional.

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