Skip to main content
Glama
Sign In
SapperMCP

SapperMCP

by MasterX1582
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Close Window

close_window

Closes a desktop window by ID or title substring, enabling targeted cleanup without affecting unrelated windows.

Instructions

Close a window gracefully 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": "close_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

C2.9/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden, and "gracefully" is the only real disclosure (a normal close rather than a force-kill). It omits critical behavior for a 0-required-parameter tool: what happens if neither selector is passed, which selector wins when both are given, and what occurs on zero or multiple title matches.

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?

A single front-loaded sentence with no filler; the selectors are stated immediately after the action. Nothing in it is redundant or padded.

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, but the tool has two optional parameters and no annotations, leaving the no-argument and dual-argument cases unexplained. For a mutation-style tool that terminates a window, the definition is thinner than its complexity warrants.

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 schema names both parameters without explaining them. The description does add genuine meaning by clarifying that title is matched as a substring and that either selector identifies the target, but it says nothing about precedence, ambiguity, or matching case/sensitivity.

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?

States a specific verb and resource ("Close a window") plus the two selector modes ("by id or title substring"), which is enough to distinguish it from focus_window, minimize_window, and restore_window. It does not explicitly name a sibling it is not, so it falls short of a 5.

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?

The description implies usage through the selectors it accepts but never says when to close versus minimize/hide, nor how to choose between window_id and title. With no exclusions or alternative-routing guidance, an agent must infer the decision from the sibling names alone.

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