EXZA Remote

Focus desktop window

exza_focus_desktop_window

Destructive

Activate a specifically named visible application window on the owner desktop, replacing the currently focused window. No keys are typed or commands run. Use exza_list_desktop_windows first to find an exact title; exza_type_desktop_text is the separate action for entering text. This changes UI focus and can redirect subsequent keyboard input, so confirm the target before approval. Requires account-bound computer:write OAuth and any prompted local owner approval.

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": {
      "name": "<name>"
    },
    "name": "exza_focus_desktop_window"
  }
}

Input Schema

Name	Required	Description	Default
`name`	Yes	Exact selected application, window or folder name; avoid guesses.

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 7, 2026

TDQS

A4.9/5.0

Behavior5/5

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

Annotations declare a destructive, non-read-only, non-idempotent mutation, and the description adds real context beyond them: it clarifies no keystrokes or commands are executed, warns that focus change can redirect subsequent keyboard input, and names the required computer:write OAuth scope plus local owner approval. That is exactly the behavioral detail annotations cannot express.

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?

Four short sentences, front-loaded with the action and effect, followed by alternatives, safety warning, and prerequisites. No filler; each sentence carries distinct information an agent needs.

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

Completeness5/5

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

For a one-parameter mutation with rich annotations and no output schema, the description covers purpose, prerequisites, authorization, side effects, and sibling routing. Nothing needed to call it correctly 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 coverage is 100% and the single parameter is already documented as an exact application/window/folder name. The description adds a meaningful constraint beyond the schema by requiring the window to be visible and by pointing at exza_list_desktop_windows as the source of the exact title, though it does not discuss name-matching behavior (case, partial matches).

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 ("Activate a specifically named visible application window") plus the scope ("on the owner desktop, replacing the currently focused window"). It explicitly separates itself from the two nearest siblings, exza_list_desktop_windows and exza_type_desktop_text, so an agent can pick it without opening any schema.

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

Usage Guidelines5/5

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

Gives an explicit prerequisite workflow ("Use exza_list_desktop_windows first to find an exact title"), names the alternative for text entry, and adds a caution to "confirm the target before approval." Both when-to-use and how-to-prepare are covered with no inference required.

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

All EXZA Remote tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?