Skip to main content
Glama

desktop_resize_window

Resize an application window to specific pixel dimensions, optionally scoped by app name or window ID, so automated desktop tasks can run at the required window size.

Instructions

agent-desktop resize-window: Resize application window

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": {
      "width": "<width>",
      "height": "<height>"
    },
    "name": "desktop_resize_window"
  }
}

Input Schema

NameRequiredDescriptionDefault
appNoFilter to application by name
widthYesNew window width in pixels
heightYesNew window height in pixels
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.3/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden, yet it discloses nothing about what happens when multiple windows match the app filter, whether the app parameter is required in practice, whether resizing is absolute or relative, or what the result/error looks like. A mutating UI tool with zero annotation coverage needs far more disclosure than a restated verb.

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 resize-window:" prefix duplicates the tool name and consumes roughly half the text with zero informational value. What remains is a single terse phrase rather than a purposeful sentence.

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 mutating window-management tool with no annotations and no output schema, the description omits the essential targeting rule (what happens if app matches several windows or neither app nor window_id is given). The schema covers parameter formats, but the agent still lacks enough to call this reliably.

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%, with each of the four parameters documented in the schema itself (width/height in pixels, app name filter, window_id from list-windows). The description adds no meaning beyond that, so the baseline 3 applies.

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

Purpose2/5

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

The description reads "agent-desktop resize-window: Resize application window," which essentially restates the tool name with a CLI-style prefix. It identifies no scope or distinguishing behavior versus siblings such as desktop_move_window or desktop_maximize, which an agent would need to choose correctly.

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 guidance, no mention of when to prefer move/maximize instead, and no prerequisites. The only hint about targeting comes from the schema's optional app/window_id fields, not the description.

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