Skip to main content
Glama
Sign In
Spacepal MCP Server

Spacepal MCP Server

by TanKucukhas
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Set Space note

set_space_note
Idempotent

Sets or replaces a short note describing what a macOS Space is for, and removes it when empty text is provided.

Instructions

Set the short note that says what a Space is for, e.g. "Client B invoices"; list_spaces returns it and Spacepal shows it in its overview. Replaces any existing note; empty text removes the note. Reversible by setting the old note again (read it from list_spaces first). Fails if the Space does not exist.

Input Schema

NameRequiredDescriptionDefault
textYesThe note, up to 500 characters. Empty text ("") removes the note.
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. Changed2 schema fields 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."
    • addedInput schema / properties / text / description
      Added value: +"The note, up to 500 characters. Empty text (\"\") removes the note."
  3. First observedv0.1.0

TDQS

A4.5/5.0
Behavior5/5

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

Beyond the annotations (idempotent, non-destructive write), the description discloses that it replaces any existing note, that empty text removes the note, that it is reversible by re-setting the old value, and that it fails if the Space does not exist. That is meaningful mutation behavior an agent needs.

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?

Three tight sentences with the purpose front-loaded, followed by visible effect, reversibility, and failure mode. No filler or repeated schema content.

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 two-parameter mutation with no output schema, the description covers purpose, effect on existing data, removal semantics, reversibility, and the failure case. 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.

Parameters3/5

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

Schema coverage is 100%, so the schema already documents maxLength, empty-string removal, and the default-to-current-Space behavior for the space parameter. The description adds only marginal semantics (what a note is for) 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 opens with a specific verb and resource ("Set the short note that says what a Space is for") and gives a concrete example note. That clearly separates it from siblings like rename_space (renames the Space itself) or set_up_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?

It explains the workflow: read the current note from list_spaces first, then call this to replace it, and set empty text to remove. It doesn't explicitly state when to pick this over rename_space, but the practical usage path is clear.

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