Skip to main content
Glama
Sign In
Spacepal MCP Server

Spacepal MCP Server

by TanKucukhas
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Current Space

current_space
Read-onlyIdempotent

Get the name and desktop number of the active macOS Space on each display to identify where the user is without listing all Spaces.

Instructions

Return the Space the user is on now: its name and desktop number (one per display). Read-only and cheaper than list_spaces when you only need the active Space.

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
spacesYesThe active Space on each display

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv0.2.3
    • changedOutput schema / properties / spaces / items / additionalProperties
      Previous value: -trueNew value: +{}
    • addedOutput schema / properties / spaces / items / properties / number / maximum
      Added value: +9007199254740991
    • addedOutput schema / properties / spaces / items / properties / number / minimum
      Added value: +-9007199254740991
  2. Changed1 schema field changedv0.2.2
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": false,
+  "properties": {
+    "spaces": {
+      "description": "The active Space on each display",
+      "items": {
+        "additionalProperties": true,
+        "properties": {
+          "apps": {
+            "description": "Apps with a window on this Space",
+            "items": {
+              "type": "string"
+            },
+            "type": "array"
+          },
+          "color": {
+            "description": "Colour as #RRGGBB",
+            "type": "string"
+          },
+          "display": {
+            "description": "Id of the display the Space is on",
+            "type": "string"
+          },
+          "id": {
+            "description": "Stable id of the Space",
+            "type": "string"
+          },
+          "isActive": {
+            "description": "True for the Space currently shown on its display",
+            "type": "boolean"
+          },
+          "isFullscreen": {
+            "description": "True for an app's full-screen Space",
+            "type": "boolean"
+          },
+          "name": {
+            "description": "Name shown in Spacepal, or \"Desktop N\" if unnamed",
+            "type": "string"
+          },
+          "note": {
+            "description": "The user's note about what the Space is for",
+            "type": "string"
+          },
+          "number": {
+            "description": "Desktop number on its display; absent for full-screen Spaces",
+            "type": "integer"
+          }
+        },
+        "required": [
+          "id",
+          "name",
+          "display",
+          "isActive",
+          "isFullscreen",
+          "apps"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "required": [
+    "spaces"
+  ],
+  "type": "object"
+}
  3. First observedv0.1.0

TDQS

A4.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is covered. The description adds value beyond them by disclosing a relative cost/latency trait versus list_spaces and a return-shape nuance (one entry per display) that annotations cannot express. It stops short of describing edge cases such as multi-display ordering or failure modes, so it is strong but not exhaustive.

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?

A single sentence, front-loaded with the core action followed by the differentiator and the cost rationale. Every clause earns its place and nothing is repeated from the annotations 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 zero-parameter read tool with a full output schema and rich annotations, the description covers purpose, selection criteria, and cost trade-off. Return-value detail is legitimately delegated to the output schema, so nothing an agent needs in order to call 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?

The tool takes zero parameters, which is the stated baseline of 4; there is no parameter meaning left to convey. The description correctly avoids inventing inputs and instead focuses on output content.

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 ("Return the Space the user is on now") plus the returned fields (name, desktop number, one per display). It explicitly contrasts with the sibling list_spaces, so an agent can choose between them 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?

Names the alternative (list_spaces) and the exact condition that selects this tool instead: "when you only need the active Space." It also supplies a tie-breaking rationale (cheaper), leaving nothing 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