Skip to main content
Glama

list_windows

List open windows and display titles only for allowlisted applications to avoid exposing document or email names.

Instructions

Open windows. Titles are shown only for allowed apps, because titles leak document and email names.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior4/5

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

With no annotations, the description carries the burden and does disclose a genuinely non-obvious behavior: titles are only shown for allowed apps because titles leak document and email names. That tells the agent to expect redacted/empty titles and not to rely on them for identification. Missing is any mention of permission requirements or how windows are identified in the response.

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?

Two short sentences with the purpose front-loaded and the privacy caveat second, where it matters most. The opening fragment "Open windows." reads slightly clipped rather than as a full statement, but nothing is wasted.

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?

A zero-parameter, output-schema-backed tool needs only purpose plus notable caveats, and both are present. The remaining gap is the absence of any prerequisite or permission note for an environment-inspection tool, which is minor given the output schema explains return values.

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?

The tool takes zero parameters, so the baseline is 4; there is nothing for the description to disambiguate. Schema coverage is also reported at 100%, leaving no gap.

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?

"Open windows" plus the name list_windows makes it clear this enumerates open windows, and the title-visibility sentence confirms windows are the returned resource. It stops short of a clean verb+object statement ("Lists all open windows") and never says what identifies each window, but the resource is unambiguous against siblings like read_window and set_text.

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 gives no when-to-use guidance, no mention of read_window or click as follow-on/alternative tools, and no statement of prerequisites. An agent must infer on its own that this is the discovery step before reading or interacting with a specific window.

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