Skip to main content
Glama
Sign In
SapperMCP

SapperMCP

by MasterX1582
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Maximize Window

maximize_window

Maximize a desktop window by window ID or title substring to bring the target application into full-screen view.

Instructions

Maximize a window by id or title substring.

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

Input Schema

NameRequiredDescriptionDefault
titleNo
window_idNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.1/5.0
Behavior2/5

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

With no annotations, the description carries the full burden and discloses almost nothing behavioral: no statement about what happens if the title substring matches multiple windows, whether maximizing is idempotent, whether the change is reversible or requires a display server, or what occurs when neither selector is supplied (both parameters are optional). Only the bare action is conveyed.

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

Conciseness4/5

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

A single front-loaded sentence with no filler; the selector mechanism is stated immediately. It is efficiently written, though the terseness leaves the behavioral gaps above unaddressed.

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

Completeness4/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-value explanation is not required, and the core action plus selectors are covered. What remains missing, mainly multi-match resolution and the both-optional/no-argument case, is real but narrow for a single-action window tool.

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 0%, so the description must compensate, and it does partially: it names both selectors and clarifies that 'title' is a substring match rather than an exact match, which the schema does not say. It omits precedence when both are given and the behavior when neither is given, which is a meaningful gap for two fully optional parameters.

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 names a specific verb and resource ('Maximize a window') and the selector mechanism ('by id or title substring'), so an agent knows exactly what action is performed. It stops short of distinguishing maximize from adjacent siblings such as fullscreen_window, restore_window, or minimize_window, which is a notable gap given how easily those overlap.

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 when-to-use guidance: nothing says when to maximize versus use fullscreen_window or restore_window, nor any prerequisite such as the window needing to already exist or be visible. Usage is only implied by the tool name itself.

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