Skip to main content
Glama

desktop_minimize

Minimize an application window by app name or window ID to clear desktop clutter and keep target windows out of the way.

Instructions

agent-desktop minimize: Minimize application window

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

Input Schema

NameRequiredDescriptionDefault
appNoFilter to application by name
window_idNoScope to a single window ID (from list-windows)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

C2.5/5.0
Behavior2/5

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

With no annotations and no output schema, the description carries the full behavioral burden, yet it says nothing about whether the application keeps running, how it can be restored, what happens when neither parameter is supplied, or what occurs with a multi-window app. 'Minimize' implies a reversible mutation, but no state or side effects are disclosed.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is short and front-loaded, but the 'agent-desktop minimize:' prefix duplicates the tool name and consumes a third of the text without adding information. The remaining clause is efficient but too thin to be considered well-structured guidance.

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?

For a mutation tool with zero annotation coverage and no output schema, the description should at minimum explain default behavior when the optional app/window_id parameters are omitted. That critical decision point is entirely absent.

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%, so both parameters (app filter and window_id scoping) are already documented. The description adds no meaning beyond the schema, which is the expected baseline when the schema carries the parameter load.

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

Purpose3/5

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

The description states a specific verb and resource ('Minimize application window'), which is more than a restatement of the name. However, it does not clarify scope (all windows of an app vs. one window) or distinguish the tool from close_app/collapse siblings, leaving the agent to infer the difference.

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 when-to-use or when-not-to-use guidance, no mention of when to prefer desktop_collapse or desktop_close_app, and no stated prerequisites. The only routing hint comes from the schema parameter descriptions.

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