Skip to main content
Glama
linux-computer-use-mcp

linux-computer-use-mcp

by dhakseshr

list_windows

Lists open X11 windows on the current workspace, topmost first, with screenshot coordinates so you can identify and focus a target window.

Instructions

List open windows on the current workspace, topmost first (X11 only), with their position in screenshot coordinates. Use focus_window to bring one to the front.

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.3.0

TDQS

A4.4/5.0
Behavior4/5

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

No annotations exist, so the description carries the burden and it delivers the important traits: an X11-only platform restriction, topmost-first ordering, and that positions are in screenshot coordinates rather than raw display space. It omits error behavior on non-X11 systems and the empty-result case, which keeps it from a 5.

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?

Two sentences, both front-loaded with the highest-value facts (scope, ordering, platform limit) before the pointer to the sibling. Every clause earns its place and nothing is repeated from the schema or annotations.

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 values need not be explained, and the description covers the remaining essentials for a parameterless read tool: platform restriction, ordering, coordinate frame, and next step. Only the failure mode on non-X11 environments is left unstated.

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 parameter semantics are not a factor and the baseline is 4. The description correctly introduces no parameter concepts the schema does not have.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('List open windows on the current workspace') and adds decisive qualifiers: scope (current workspace), ordering (topmost first), platform constraint (X11 only), and return semantics (position in screenshot coordinates). This is enough to distinguish it from list_applications and screenshot without opening either schema.

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

Usage Guidelines4/5

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

Explicitly routes the follow-up action: 'Use focus_window to bring one to the front,' which tells the agent what this tool does not do. It stops short of stating exclusions against adjacent tools like list_applications or screenshot, so it is clear context rather than a full when/when-not map.

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