Skip to main content
Glama
Sign In
Computer Use MCP Server

Computer Use MCP Server

by SebastianBaltes
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

computer_key

Press a key or key combination on a Linux desktop. Uses xdotool names for modifiers, function keys, and shortcuts.

Instructions

Press a key or key combination. Use xdotool key names: Return, Tab, Escape, BackSpace, Delete, space, Up, Down, Left, Right, Home, End, Page_Up, Page_Down, F1-F12, ctrl+c, ctrl+v, ctrl+z, alt+F4, super, ctrl+shift+t, etc. Multiple keys can be chained with '+' for combos.

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": "computer_key"
  }
}

Input Schema

NameRequiredDescriptionDefault
keysYesKey or key combination (e.g. 'ctrl+s', 'Return', 'alt+Tab')

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4/5.0
Behavior3/5

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

No annotations provided; description mentions xdotool key names but not side effects, error handling, or permissions.

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?

Two sentences, front-loaded with action, examples concise.

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?

Simple one-param tool; explanation adequate for usage, though could mention output (none).

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 100% (baseline 3); description adds key name conventions and chaining with '+', beyond schema.

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?

Clearly states 'Press a key or key combination', distinguishing from siblings like computer_type (typing text) and computer_hold_key (holding).

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?

Provides examples but lacks explicit when-to-use vs alternatives like computer_hold_key or computer_type.

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

Deploy Server

Other Tools