Skip to main content
Glama
kuhyx

i3wm-mcp

Move i3 Window

move_window

Move the focused container or a selected window by class/title to a direction, workspace, output, scratchpad, or screen center.

Instructions

Move the focused container (or one matched by class/title/instance/mark/con_id) to exactly one destination: a direction (with pixel amount), a workspace, an output, the scratchpad, or a screen position (center). Reversible; returns per-command success. To change focus rather than move, use focus_window; to move whole workspaces between monitors, use manage_workspace.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
markNoSelect the window to move by mark (criteria).
titleNoSelect the window to move by title (criteria).
con_idNoSelect the window to move by exact i3 id (criteria).
instanceNoSelect the window to move by WM_CLASS instance (criteria).
amount_pxNoPixels to move when `direction` is set. Default 10.
directionNoMove the container this direction.
to_centerNoCenter a floating container on its output. Default false.
to_outputNoMove the container to this output, e.g. 'HDMI-1'.
to_workspaceNoMove the container to this workspace (name or number).
window_classNoSelect the window to move by X11 class (criteria).
to_scratchpadNoMove the container to the scratchpad. Default false.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
errorNoFirst error message across the payload, or null on full success.
successYesTrue only if every command in the payload succeeded.
outcomesNoPer-command outcomes, in payload order.
Behavior4/5

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

Beyond annotations (readOnlyHint=false, destructiveHint=false), the description adds 'Reversible; returns per-command success.' This discloses reversibility and return format, though it doesn't detail side effects or auth requirements.

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

Conciseness5/5

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

Three sentences with clear front-loading: purpose first, then constraint, then sibling differentiation. No extraneous words.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a tool with 11 parameters, 0 required, 100% schema coverage, and output schema, the description covers destination types, selection options, reversibility, and sibling tools. Missing clarification on criteria combination, but adequate.

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 baseline is 3. The description adds the constraint 'exactly one destination' but doesn't elaborate on parameter formats or interactions beyond the schema.

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

Purpose5/5

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

The description clearly states the tool moves a container, specifies selection options (class/title/instance/mark/con_id), and lists possible destinations (direction, workspace, output, scratchpad, screen center). It distinguishes from sibling tools focus_window and manage_workspace.

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

Usage Guidelines5/5

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

Explicitly tells when to use this tool vs alternatives: 'To change *focus* rather than move, use focus_window; to move whole workspaces between monitors, use manage_workspace.' Also notes 'exactly one destination' to avoid conflicting parameters.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/kuhyx/i3wm-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server