Skip to main content
Glama

desktop_list_windows

List all visible desktop windows to inventory open applications, and filter by exact application name to focus on a specific app.

Instructions

agent-desktop list-windows: List all visible windows (--app to filter by application)

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

Input Schema

NameRequiredDescriptionDefault
appNoFilter to application by exact case-insensitive name
timeout_msNoInventory deadline in milliseconds (default 5000)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

C2.9/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 discloses only that windows are 'visible', but says nothing about whether minimized/hidden windows are excluded, what ordering is used, what identifiers are returned, or how the timeout_ms deadline behaves on expiry.

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 short sentence with the core action front-loaded. The 'agent-desktop list-windows:' prefix is redundant noise, but the rest is efficient.

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?

With no annotations and no output schema, the description should explain what a listed window looks like (IDs/handles needed by desktop_focus_window) and the timeout behavior. For a discovery tool feeding downstream window operations, this is a significant gap.

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 100%, so both parameters are already documented in the schema. The description's '--app to filter by application' merely restates the app parameter in CLI syntax and adds no new meaning; baseline 3 applies.

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 ('List all visible windows') and adds the filtering capability, which distinguishes it from siblings like desktop_list_apps or desktop_focus_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?

No guidance on when to use this versus desktop_list_apps, desktop_find, or desktop_focus_window, and no mention of prerequisites or follow-up steps. The agent must infer that this is the entry point for discovering windows before focusing or manipulating them.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.