Skip to main content
Glama
Sign In
Spacepal MCP Server

Spacepal MCP Server

by TanKucukhas
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Set up Space

set_up_space

Switch to a Space and open the apps, URLs, and files its automation lists to prepare a workspace, including on-enter actions.

Instructions

Switch to a Space and open the apps, URLs and files its Spacepal automation lists, even if they were opened before. Entering the Space also runs its usual on-enter actions, such as a Shortcut. Use it to prepare a workspace; to only change the visible Space use switch_space. Opens apps on the user's Mac, so it cannot be undone automatically. Does nothing beyond switching if the Space has no automation. Fails if the Space does not exist.

Input Schema

NameRequiredDescriptionDefault
spaceNoWhich Space: desktop number or name from list_spaces. Leave it out for the Space the user is on now.

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: +"Which Space: desktop number or name from list_spaces. Leave it out for the Space the user is on now."
  3. Addedv0.2.0

TDQS

A4.7/5.0
Behavior5/5

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

Beyond the annotations it discloses the side effects (opens apps on the user's Mac, runs on-enter actions like a Shortcut), the reversibility caveat ('cannot be undone automatically'), the re-open behavior, the no-automation no-op, and the failure mode for a missing Space. The 'cannot be undone automatically' caveat refines rather than contradicts destructiveHint=false, since no data is destroyed.

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 tight sentences ordered purpose → routing → side effects → edge cases, with the core action front-loaded. Every sentence carries distinct information with no restatement of the name or schema.

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 one-parameter, non-read-only tool with no output schema, the description covers the action, its irreversible-ish effects, the no-op case, and the failure condition. Nothing an agent needs in order to call it safely is missing.

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 single 'space' parameter is already documented with its integer-or-name options and the default-to-current-Space behavior. The description adds no syntax or selection detail beyond the schema, so the baseline 3 applies.

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 uses a specific verb+resource ('Switch to a Space and open the apps, URLs and files its Spacepal automation lists') and explicitly contrasts itself with the sibling switch_space, so an agent can distinguish the two without opening either schema.

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?

It states the intended use ('prepare a workspace'), names the alternative and the selecting condition ('to only change the visible Space use switch_space'), and adds a when-not case ('Does nothing beyond switching if the Space has no automation').

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