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

linux-computer-use-mcp

by dhakseshr

press_key

Simulates key presses and keyboard shortcuts on a Linux desktop, including repeats and optional screenshots, to automate text entry, navigation, and app control.

Instructions

Press a key or shortcut, e.g. "Return", "Escape", "ctrl+s", "ctrl+l", "alt+Tab", "super", "F5".

Aliases like enter, esc, cmd/win (= super), pgdn, del are accepted.

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

Input Schema

NameRequiredDescriptionDefault
keysYes
repeatNo
screenshotNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations exist, so the description carries the entire burden and largely does not. It never says which window receives the keystroke, whether modifier combos are pressed and released atomically, or that a screenshot is captured by default — all behaviors an agent needs to predict side effects.

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?

Two short sentences, with the core capability and the example list front-loaded where it matters most for key-syntax disambiguation. The alias sentence is compact and earns its place; nothing is padded.

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?

For a three-parameter UI-control tool with no annotations and no output schema, the definition omits too much: undocumented 'repeat' and 'screenshot' parameters, no statement about output (does it return an image?), and no target-window semantics.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0%, and the description only documents the 'keys' format plus alias mapping (enter, esc, cmd/win, pgdn, del), which is genuinely useful. The 'repeat' and, more importantly, 'screenshot' parameters — whose default is true — are never mentioned, leaving a surprising side effect undisclosed.

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?

States a concrete verb ('Press') and resource ('a key or shortcut') and backs it with six real examples spanning single keys, modifiers, and function keys. It does not explicitly distinguish itself from siblings like hold_key or type_text, so it stops short of a 5.

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

Usage Guidelines3/5

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

Usage is only implied through the examples; there is no statement of when to prefer this over hold_key (press-and-hold) or type_text (text entry), and no prerequisites such as a focused window. An agent can infer the intent but must guess the boundary cases.

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