Skip to main content
Glama

desktop_focus_window

Brings a specified desktop window to the front and confirms it receives operating system focus, so users can reliably direct input to the intended app or window.

Instructions

agent-desktop focus-window: Bring a window to front and confirm OS focus

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_focus_window"
  }
}

Input Schema

NameRequiredDescriptionDefault
appNoApplication name
titleNoWindow title (partial match accepted)
window_idNoWindow ID from list-windows

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 supplied, so the description carries the full disclosure burden. "Confirm OS focus" hints that the call verifies focus at the OS level, but the description never says what happens on failure (window not found, ambiguous partial title match, minimized/occluded window), whether OS accessibility permissions are required, or whether the call blocks.

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 short, front-loaded sentence with no filler. The only waste is the "agent-desktop focus-window:" prefix, which merely restates the tool name before the useful content.

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?

The tool takes three optional identifiers with zero required parameters, has no output schema, and has no annotations — a combination that demands more explanation than one clause. The description does not cover the zero-argument case, identifier precedence, failure behavior, or what the promised focus confirmation looks like.

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 app, title, and window_id are already documented in the schema, and the description adds nothing about them. It is silent on the important semantics — precedence when multiple identifiers are supplied, and what happens when all three optional parameters are omitted.

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?

"Bring a window to front and confirm OS focus" states a concrete verb (focus/raise) and resource (a window), and adds the confirming-focus nuance beyond the name. It does not, however, distinguish itself from the sibling desktop_focus, so an agent cannot tell from the text alone which of the two to pick.

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?

There is no when-to-use guidance, no exclusions, and no reference to any alternative — notably the sibling desktop_focus, which by name appears to overlap. The agent must infer the selection rule from tool names, which the instructions say is not sufficient.

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