Skip to main content
Glama
Sign In
Spacepal MCP Server

Spacepal MCP Server

by TanKucukhas
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Remove desktop

remove_desktop
Destructive

Close a desktop to move its windows to another desktop without closing them; confirm with the user first because Spacepal names, notes, and automations are lost.

Instructions

Close a desktop, as with its close button in Mission Control. Its windows move to another desktop and are not closed, but its Spacepal name, note and automation are lost and cannot be restored automatically. Full-screen Spaces cannot be removed this way. Always ask the user before calling this. Fails if the Space does not exist.

Input Schema

NameRequiredDescriptionDefault
spaceYesDesktop number or name from list_spaces

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"
  3. Addedv0.2.0

TDQS

A4.5/5.0
Behavior5/5

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

Annotations already flag destructiveHint=true and non-idempotence, but the description still adds substantial context beyond them: windows are preserved and relocated, while the name, note and automation are permanently lost, plus a specific failure condition ('fails if the Space does not exist'). It also states a mandatory consent gate, which is not encoded in any annotation.

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?

Five short sentences, each carrying distinct information: operation, side effect on windows, irreversible data loss, exclusion, consent requirement, and failure mode. Front-loaded with the action and free of padding.

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 destructive tool with no output schema, the description covers everything an agent needs: what is destroyed, what survives, what is refused, when to check with the user, and how it fails. Nothing material is left unstated.

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 already documents itself as a desktop number or name from list_spaces. The description only indirectly reinforces that the Space must exist; it adds no syntax, format, or selection guidance beyond the schema. 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?

Names a specific verb and resource (close a desktop) and anchors it to a concrete mental model ('as with its close button in Mission Control'), which unambiguously separates it from the add_desktop sibling. An agent knows exactly what operation this performs without opening the schema.

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?

Explicit when-to-use constraint ('Always ask the user before calling this') and a clear exclusion ('Full-screen Spaces cannot be removed this way'). It falls short of naming an alternative route for the excluded case (e.g., what to do for full-screen Spaces, or which sibling preserves the name/note), leaving that to inference.

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