Skip to main content
Glama

desktop_move_window

Move an application window to a new screen position by specifying X and Y coordinates, optionally filtering by app or window ID.

Instructions

agent-desktop move-window: Move application window to new position

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": {
      "x": "<x>",
      "y": "<y>"
    },
    "name": "desktop_move_window"
  }
}

Input Schema

NameRequiredDescriptionDefault
xYesNew window X position; write a negative value with = (--x=-100)
yYesNew window Y position; write a negative value with = (--y=-100)
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: it does not say whether the move is absolute screen coordinates, what happens if the app or window_id does not match, whether failures raise errors, or whether OS accessibility permissions are required. For a state-mutating UI tool with zero annotation coverage, this is a substantial gap.

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, front-loaded sentence with no filler, though the redundant 'agent-desktop move-window:' label consumes part of the very limited text budget.

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?

With no annotations, no output schema, and no return or failure information, the definition leaves an agent unable to predict outcomes or diagnose a failed move. A mutation tool taking required coordinates needs at least a note on coordinate space, targeting behavior, and error conditions.

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 x, y, app, and window_id all documented in the schema, including the negative-value syntax. The description adds no meaning beyond that, 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?

States a specific verb ('Move') and resource ('application window') plus the outcome ('to new position'), so an agent can tell what it does. It offers no differentiation from siblings such as desktop_resize_window or desktop_focus_window, and the 'agent-desktop move-window:' prefix merely restates the tool name.

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 use this tool versus desktop_focus_window, desktop_resize_window, or desktop_batch, and no stated preconditions (for example, that the target window must exist or be identified via list-windows). The only hint of scoping comes from the schema's 'window_id ... from list-windows' description, not from the description text.

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