Spacepal MCP Server

Overview Schema Source Related Servers Discussions Admin

Open overview

open_overview

Displays a full-screen overview of all Spaces with live previews so you can inspect and pick one; call again to close it. Requires a Spacepal trial or license.

Instructions

Show Spacepal's full-screen overview of every Space with live previews, for the user to look at and pick from. It is a toggle: calling it while the overview is open closes it. Changes nothing else. Needs Spacepal's trial or a license; without one Spacepal shows its license window instead. To get the Space list as data, use list_spaces.

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": "open_overview"
  }
}

Input Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Nov 5, 2026

TDQS

A5/5.0

Behavior5/5

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

Annotations declare non-idempotent and non-read-only but say nothing about why; the description supplies the exact reason — it is a toggle, so a second call closes the overview — plus a scope guarantee ('Changes nothing else') and the licensing side effect. This is materially more than the annotations provide and is consistent with them.

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 short sentences, front-loaded with the action and each carrying distinct value: toggle semantics, scope guarantee, license gate, alternative tool. No filler or repetition.

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 no-parameter UI-navigation tool with no output schema, the description covers the surprising semantics (toggle), the prerequisite, and the sibling routing decision. An agent has everything needed to call it or avoid calling it.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

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

Zero parameters, so there is nothing to disambiguate and the schema is trivially complete. The description correctly does not waste space restating an empty schema.

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 ('Show Spacepal's full-screen overview of every Space with live previews') and explicitly contrasts with the sibling list_spaces, which returns the list as data. An agent can distinguish UI-navigation from data-retrieval 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?

Gives explicit when-to-use (user picks a Space visually), an explicit alternative ('To get the Space list as data, use list_spaces'), and a precondition gate (trial or license required, otherwise the license window appears). Nothing is left to inference.

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