Skip to main content
Glama
Sign In
Spacepal MCP Server

Spacepal MCP Server

by TanKucukhas
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Switch Space

switch_space
Idempotent

Switch to another macOS Space instantly without the slide animation by desktop number, name, next, previous, or back; only the visible Space changes, and windows stay put.

Instructions

Show another Space on the user's screen, instantly and without the slide animation. Give a desktop number or name from list_spaces, or "next", "previous" (neighbouring desktop) or "back" (the Space shown before). Changes only what is visible; no windows move. Undo with space="back". Returns the Space now shown; fails if no Space has that name.

Input Schema

NameRequiredDescriptionDefault
spaceYesDesktop number or name from list_spaces, or one of "next", "previous", "back".

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.2.3
    • 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"
+  }
+]
  2. Changed1 schema field changedv0.2.2
    • changedInput schema / properties / space / description
      Previous value: -"Desktop number (1, 2, ...) or Space name, e.g. \"Mail\"."New value: +"Desktop number or name from list_spaces, or one of \"next\", \"previous\", \"back\"."
  3. First observedv0.1.0

TDQS

A4.7/5.0
Behavior5/5

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

Annotations already declare non-read-only, idempotent, non-destructive, but the description adds genuinely non-derivable context: the switch is instant with no slide animation, only visibility changes and no windows move, it returns the Space now shown, and it fails when the name is unknown. That is exactly the mutation-scope and failure-mode detail the annotations cannot convey.

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?

Four short sentences, each carrying distinct information: action and effect, accepted value forms, non-effects, return and failure mode. The scope constraint is front-loaded and nothing is redundant.

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 tool with no output schema, the description covers the accepted values, the visible side effect, the return value, and the error condition. Nothing an agent needs to invoke it correctly is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3, but the description goes further by defining 'back' as the Space shown before and 'next'/'previous' as neighbouring desktops, which the schema only lists without meaning. It also states the failure behavior for an unrecognized name, adding real semantic value.

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 ('Show another Space on the user's screen') plus a distinguishing qualifier ('instantly and without the slide animation'). It also implicitly separates itself from move_window_to_space with 'no windows move', so an agent can tell it apart from siblings without opening schemas.

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?

Explicitly routes the agent to list_spaces for valid names/numbers and names three special tokens including 'back' for undo, which is clear usage guidance. It does not state exclusions against read-only siblings like current_space or list_spaces, but the practical when-to-use guidance is strong.

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

Deploy Server

Other Tools