Skip to main content
Glama
Sign In
SapperMCP

SapperMCP

by MasterX1582
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Fullscreen Window

fullscreen_window

Toggle a window's fullscreen state to maximize screen space for the active task. Target a window by title or ID with a boolean on/off setting.

Instructions

Toggle fullscreen state of a window.

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

Input Schema

NameRequiredDescriptionDefault
onNo
titleNo
window_idNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.4/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden. It does not explain whether the tool requires an existing window, how title/window_id selection works, whether changes are reversible, what happens on failure, or what the output contains.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The single sentence is front-loaded and concise, but it is under-specified rather than optimally concise. It does not waste words, but it also does not earn its place by adding enough operational detail.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists, so return values need not be described. However, for a window-mutating tool with no annotations and three undocumented parameters, the definition omits critical context about targeting, behavior, and side effects.

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

Parameters1/5

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

Schema description coverage is 0% for all three parameters. The description does not explain the 'on' boolean, the 'title' selector, or the 'window_id' selector, and the word 'toggle' is potentially ambiguous alongside an explicit 'on' parameter.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb and resource: 'Toggle fullscreen state of a window.' It is clear about the action, but it does not differentiate from similar window-state siblings like maximize_window or restore_window.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no guidance on when to use fullscreen versus maximize_window, minimize_window, restore_window, or focus_window. The implied usage is simply that the tool changes fullscreen state, but no prerequisites or exclusions are given.

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