Skip to main content
Glama
Sign In
codex-computer-use-linux

codex-computer-use-linux

by maxionice
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Press a keyboard key

press_key

Press an allow-listed key in the active Linux app, optionally with ctrl, alt, shift, or super modifiers, for desktop automation.

Instructions

Press one allow-listed key with optional ctrl, alt, shift, or super modifiers in the focused Linux app.

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

Input Schema

NameRequiredDescriptionDefault
keyYes
modifiersNo
interval_msNo

Output Schema

NameRequiredDescriptionDefault
okNo
actionYes
backendYes
messageYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior3/5

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

Annotations indicate the tool is not read-only, so a side effect is expected. The description adds that the key must be allow-listed and that the action targets the focused Linux app, which is useful context, but it does not elaborate on potential side effects or restrictions beyond that.

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?

The description is a single, well-structured sentence that conveys the essential purpose, scope, and modifier options without unnecessary detail.

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

Completeness3/5

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

For a tool with only one required parameter, the description is mostly adequate, but the undefined 'allow-listed' key set is a notable gap. It does not specify which keys are accepted, which could lead to failed invocations. However, the output schema exists, so return values are not the responsibility of the description.

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 description coverage is 0%, so the description must compensate. It mentions the key and modifier options, but does not explain the interval_ms parameter, and the 'allow-listed key' set is left undefined. Thus, parameter semantics are only partially addressed.

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?

The description uses a specific verb ('Press') and resource ('key'), clearly stating the action is a single key press with optional modifiers in the focused Linux app. This distinguishes it from related tools like type_text and click.

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?

The description clearly communicates when to use this tool: pressing a key with modifiers in the focused Linux app. It implies a distinction from text typing or mouse actions, though it does not explicitly name alternative tools or exclusion criteria.

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