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

linux-computer-use-mcp

by dhakseshr

focus_window

Bring a window to the front by matching part of its title or app class to focus it, avoiding manual Alt+Tab or overview navigation.

Instructions

Bring a window to the front and focus it, matched by part of its title or app class, e.g. "Chrome", "WhatsApp", "Terminal". Much faster and more reliable than clicking through the overview or Alt+Tab (X11 only).

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "query": "<query>"
    },
    "name": "focus_window"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYes
screenshotNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.0

TDQS

A3.7/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden; it does disclose the X11-only limitation and the partial-match targeting behavior, which is useful. However, it never says what happens when no window matches (error vs. silent no-op) or that a screenshot is captured by default, leaving meaningful side-effect and failure information undisclosed.

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?

The core action and matching rule are front-loaded in the first sentence, followed by rationale and the platform caveat. Every clause carries information; nothing is padding.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The tool is simple (two parameters, no output schema), so the bar is modest, but with no output schema the description should indicate what comes back (notably the default screenshot) and what failure looks like. Those gaps keep it at minimum-viable rather than complete.

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 description coverage is 0%, so the description must compensate; it does well for 'query' by explaining partial title/app-class matching and giving literal examples. The 'screenshot' parameter, which defaults to true and implies a side effect plus a return artifact, is never mentioned, so half the parameters remain undocumented everywhere.

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?

The description uses a specific verb and resource: 'Bring a window to the front and focus it,' and clarifies the matching rule ('by part of its title or app class') with concrete example queries like "Chrome" and "Terminal." It is clearly distinct from creation-oriented siblings such as open_application, though it never names a sibling to route against.

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?

It gives real usage guidance by positioning itself against manual alternatives: 'Much faster and more reliable than clicking through the overview or Alt+Tab,' and states a hard platform constraint '(X11 only),' which effectively tells the agent when the tool will not work. It stops short of an explicit when-not-to-use rule or a named alternative tool.

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