EXZA Remote

Send desktop shortcut

exza_send_desktop_shortcut

Destructive

Send one keyboard shortcut to the current desktop application. This may trigger irreversible UI actions; do not confuse it with exza_type_desktop_text for literal text. 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": {
      "key": "<key>"
    },
    "name": "exza_send_desktop_shortcut"
  }
}

Input Schema

Name	Required	Description	Default
`key`	Yes	Supported key or shortcut to send to the focused desktop window.
`modifiers`	No	Keyboard modifiers for shortcut; may trigger application actions.

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 7, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already declare destructiveHint=true, idempotentHint=false and readOnlyHint=false, but the description adds real context beyond them: the warning about irreversible UI actions and the two-layer authorization model (account-bound computer:write OAuth plus prompted local owner approval). It does not say what occurs on an unsupported key or how failures surface.

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?

Three short sentences, front-loaded with the action, then the risk/sibling disambiguation, then the prerequisites. No filler and nothing buried.

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?

For a two-parameter, no-output-schema tool with rich annotations, the description covers purpose, hazard, sibling disambiguation and auth requirements. Only the focus precondition and error/return behavior are unaddressed, which keeps it just short of 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 100%, so both 'key' and 'modifiers' are already documented, and the description adds no syntax examples (e.g. 'ctrl+c' vs separate modifiers) or accepted key vocabulary. Baseline 3 applies since the schema carries the parameter burden.

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 ('Send one keyboard shortcut to the current desktop application') and immediately names the sibling it must not be confused with, exza_type_desktop_text. An agent can distinguish this from text typing 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?

Gives a clear when-to-use (send a shortcut to the focused app) and an explicit exclusion routing literal text to exza_type_desktop_text. It does not mention that a window must already be focused (e.g. via exza_focus_desktop_window) or what to do when the target app is not frontmost, which is the remaining gap.

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?