Spacepal MCP Server

Overview Schema Source Related Servers Discussions Admin

Move window to Space

move_window_to_space

Move the frontmost macOS window to another Space by desktop number, name, next, or previous, keeping its size and position.

Instructions

Move the user's frontmost window to another Space; the window keeps its size and position. Target is a desktop number or name from list_spaces, or "next"/"previous". The frontmost window is the one the user last focused: from a terminal client that is usually the window they worked in, from Claude Desktop it is Claude's own window. On macOS 14.0-14.4 and 26.4+ the window moves directly; on other versions Spacepal drags it, which takes a moment. Depending on the user's settings the screen may follow the window. Undo by moving it back. Fails if no Space has that name.

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": {
      "space": "<space>"
    },
    "name": "move_window_to_space"
  }
}

Input Schema

Name	Required	Description	Default
`space`	Yes	Target desktop number or name from list_spaces, or "next" / "previous".

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedv0.2.3Nov 6, 2026

removedInput schema / additionalProperties
```
Removed value: -false
```

changedInput schema / properties / space / anyOf

Previous value: -[
-  {
-    "exclusiveMinimum": 0,
-    "type": "integer"
-  },
-  {
-    "minLength": 1,
-    "type": "string"
-  }
-]New value: +[
+  {
+    "exclusiveMinimum": 0,
+    "maximum": 9007199254740991,
+    "type": "integer"
+  },
+  {
+    "minLength": 1,
+    "type": "string"
+  }
+]

Changed1 schema field changedv0.2.2Nov 6, 2026

changedInput schema / properties / space / description

Previous value: -"Desktop number (1, 2, ...) or Space name, e.g. \"Mail\"."New value: +"Target desktop number or name from list_spaces, or \"next\" / \"previous\"."

First observedv0.1.0Nov 5, 2026

TDQS

A4.4/5.0

Behavior5/5

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

Goes well beyond the annotations: it discloses OS-version-dependent execution (direct move on macOS 14.0-14.4 and 26.4+, otherwise a drag that 'takes a moment'), that the screen may follow the window depending on settings, that the operation is reversible, and the failure condition when no Space matches the name. This is exactly the behavioral context annotations cannot carry.

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?

Front-loaded with the action and then layered with the details an agent needs, with no filler sentences. Some clauses about client-specific frontmost-window behavior could be tightened, but each carries real operational meaning.

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

Completeness5/5

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

For a single-parameter mutation tool with modest annotations and no output schema, the description covers target selection, environment-dependent latency, side effects (screen following), reversibility, and failure mode. An agent has everything needed to call it and interpret the outcome.

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% and the parameter's own description already states 'Target desktop number or name from list_spaces, or "next" / "previous"' nearly verbatim. The description's added value is limited to clarifying that list_spaces is the source of valid names/numbers, so it does not meaningfully exceed the schema baseline.

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?

States a specific verb and resource ('Move the user's frontmost window to another Space') and adds the key scoping detail that the window keeps its size and position. The 'frontmost window' qualifier distinguishes this from a general Space-switching tool like switch_space.

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

Usage Guidelines4/5

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

Explains how to specify the target (desktop number or name from list_spaces, or "next"/"previous") and gives a recovery path ('Undo by moving it back'). It stops short of explicitly contrasting with the sibling switch_space, so the choice between moving a window and switching the Space is only implied.

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