Spacepal MCP Server

Overview Schema Source Related Servers Discussions Admin

Restore sessions

restore_sessions

Reopen terminal and Chrome windows saved by save_sessions, each on its original Space. Use this to recover saved sessions; it opens new windows rather than moving existing ones.

Instructions

Reopen the terminal and Chrome windows saved by save_sessions, each on the Space it was saved from. Opens new windows, so calling it twice can open duplicates. Needs Spacepal's trial or a license. To move windows that are already open, use restore_window_layout instead.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "restore_sessions"
  }
}

Input Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Addedv0.2.0Nov 6, 2026

TDQS

A4.9/5.0

Behavior5/5

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

The description goes beyond simple operation hints by disclosing critical behavioral traits: that duplicate windows may open if called twice, and that the functionality requires a specific license/trial status to operate.

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?

The description is highly efficient, front-loading the primary definition and then layering crucial constraints (duplication, licensing) and usage alternatives concisely.

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?

Given that there is no output schema, the description provides complete behavioral context by covering scope (Chrome/Terminal), state changes (new windows opened), and operational limitations (licensing/duplicates).

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?

Since the tool accepts zero parameters, the schema provides no descriptive content, meaning the description cannot add semantic meaning beyond the baseline score.

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 explicitly states what is restored (terminal and Chrome windows) and precisely references the source (`save_sessions`), making the purpose unambiguous and distinct from other window management siblings.

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 provides clear guidance on alternatives by specifically instructing the user to use `restore_window_layout` if the goal is to move already open windows, not restore sessions.

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