Skip to main content
Glama

desktop_maximize

Maximizes or zooms a desktop application window to fill the screen; target a specific app or window ID to control the right window.

Instructions

agent-desktop maximize: Maximize or zoom 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_maximize"
  }
}

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

B3.1/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 whether the call is idempotent, whether it toggles (restoring an already-maximized window), what happens if the app is not running, or what it returns. These are the questions an agent needs answered before invoking a window-state mutation.

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?

A single short sentence with the action front-loaded and no padding. The 'agent-desktop maximize:' prefix largely restates the tool name and could be dropped, but the rest is efficient.

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?

Both parameters are optional, so the no-argument behavior (maximize everything? the frontmost window?) is undefined in description, schema, and annotations alike, and there is no output schema to fall back on. For a state-changing desktop tool with zero structured guidance, this leaves real gaps an agent can only discover by trial.

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 coverage is 100%, so both parameters (app filter, window_id from list-windows) are already documented in structured data. The description adds no new meaning about filtering precedence when both are supplied or what the zero-argument case does, so the baseline 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?

States a specific verb (maximize/zoom) and resource (application window), so the agent knows the operation. It does not distinguish this from near-siblings like desktop_expand, desktop_collapse, or desktop_focus_window, and 'maximize or zoom' leaves ambiguity about which platform behavior applies.

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

Usage Guidelines3/5

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

Usage is only implied by the verb; there is no explicit statement of when to prefer this over desktop_expand, desktop_focus_window, or desktop_collapse, and no prerequisites such as whether the window must already be focused or open. The 'from list-windows' hint for window_id is the only contextual cue.

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