Skip to main content
Glama

List windows

windows
Read-onlyIdempotent

Lists open desktop applications and dialogs with IDs, apps, titles, and PIDs; filter by title or app to locate and target a specific UI surface. Password managers are excluded.

Instructions

Application windows on the desktop (id, app, title, pid), like the taskbar, plus open dialogs (a file "Open" box…) with dialogOf: the window that owns them; look at a dialog by its id or title. Password managers are never listed. filter: part of a title or app.

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

Input Schema

NameRequiredDescriptionDefault
filterNo

Output Schema

NameRequiredDescriptionDefault
windowsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv3.7.4
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "properties": {
      +    "windows": {
      +      "items": {
      +        "properties": {
      +          "app": {
      +            "description": "process:<path> or the Store app id",
      +            "type": "string"
      +          },
      +          "dialogOf": {
      +            "properties": {
      +              "id": {
      +                "type": "integer"
      +              },
      +              "title": {
      +                "type": "string"
      +              }
      +            },
      +            "required": [
      +              "id"
      +            ],
      +            "type": "object"
      +          },
      +          "id": {
      +            "type": "integer"
      +          },
      +          "nativeOnly": {
      +            "type": "boolean"
      +          },
      +          "owner": {
      +            "description": "id of the window that owns this dialog",
      +            "type": "integer"
      +          },
      +          "pid": {
      +            "type": "integer"
      +          },
      +          "title": {
      +            "type": "string"
      +          }
      +        },
      +        "required": [
      +          "id",
      +          "app",
      +          "title"
      +        ],
      +        "type": "object"
      +      },
      +      "type": "array"
      +    }
      +  },
      +  "required": [
      +    "windows"
      +  ],
      +  "type": "object"
      +}
  2. First observedv0.1.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already cover read-only, idempotent, non-destructive and closed-world, so the description's main value-add is the privacy exclusion: 'Password managers are never listed.' It also discloses that dialogs appear alongside windows, which an agent would not otherwise expect.

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?

One compact, front-loaded passage with zero filler; the semicolon-chained clauses and parenthetical examples are dense but each carries real information. Slightly telegraphic, which costs a bit of readability.

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 shape need not be spelled out, yet the description still flags the key fields and the dialogOf link. For a single-optional-param listing tool this is essentially complete; only explicit sibling routing is missing.

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?

Schema description coverage is 0%, so the description must carry the parameter. It does: 'filter: part of a title or app', clarifying substring matching and which fields are matched — meaning the bare string schema would not convey.

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?

Names the specific resource (application windows plus open dialogs) and the fields returned (id, app, title, pid), and explains the dialogOf ownership relation. It does not explicitly contrast with the sibling 'window' tool, so an agent must infer which to call.

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

Usage Guidelines3/5

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

Usage is implied rather than stated: 'look at a dialog by its id or title' hints at how to address a dialog afterwards, but there is no explicit when-to-use-this-vs-'window'/'look' guidance or precondition statement.

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