Skip to main content
Glama

desktop_restore

Restore minimized or maximized desktop windows to their normal state, optionally filtering by application name or window ID to target a specific window.

Instructions

agent-desktop restore: Restore minimized or maximized 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_restore"
  }
}

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.9/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden, and it discloses almost nothing beyond the action name. It does not say whether restore is a toggle, whether restoring a non-minimized/non-maximized window fails, whether it changes focus or z-order, or what permissions or side effects are involved.

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

Conciseness4/5

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

It is a single, short, front-loaded sentence with no padding. The 'agent-desktop restore:' prefix is mildly redundant with the tool name but costs little.

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?

With only two optional, fully documented parameters and no output schema, the structured fields cover most of what an agent needs to invoke it. However, with zero annotations the description should compensate for the missing behavioral profile (mutation semantics, edge-case results), which it does not.

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 explains 'app' as an application-name filter and 'window_id' as a scope referencing list-windows. The description adds no further parameter meaning, so the baseline of 3 applies.

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?

The description gives a specific verb (restore) and resource (a minimized or maximized window), so the agent knows exactly which state transition it performs. It does not name the related siblings (desktop_minimize, desktop_maximize, desktop_collapse/expand), so differentiation is left to inference from names alone.

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?

The phrase 'minimized or maximized window' hints at the applicable state, but there is no explicit when-to-use/when-not-to-use guidance and no mention of the maximize/minimize siblings as alternatives. An agent must infer whether calling this on a normal window is a no-op or an error.

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