Skip to main content
Glama
tmustier

codex-computer-use-mcp

by tmustier
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Local

press_key

Send a key or key-combination press to a specified app, including modifier and navigation keys. Supports xdotool syntax for special keys.

Instructions

Press a key or key-combination on the keyboard, including modifier and navigation keys. This supports xdotool's key syntax, for example a, Return, super+c, Up, or KP_0.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
appYesApp name, full app path, or unambiguous bundle identifier
keyYesKey or key combination to press

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed2 schema fields changedv0.5.0
    • addedInput schema / $defs
      Added value: +{
+  "__schema0": {
+    "anyOf": [
+      {
+        "type": "string"
+      },
+      {
+        "type": "number"
+      },
+      {
+        "type": "boolean"
+      },
+      {
+        "type": "null"
+      },
+      {
+        "items": {
+          "$ref": "#/$defs/__schema0"
+        },
+        "type": "array"
+      },
+      {
+        "additionalProperties": {
+          "$ref": "#/$defs/__schema0"
+        },
+        "propertyNames": {
+          "type": "string"
+        },
+        "type": "object"
+      }
+    ]
+  }
+}
    • changedInput schema / additionalProperties
      Previous value: -falseNew value: +{
+  "$ref": "#/$defs/__schema0"
+}
  2. Addedv0.3.0

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already signal that the action is not read-only, idempotent, or destructive, but they do not carry the burden since they default to false. The description adds the xdotool key syntax detail, which reveals compatibility, but does not mention focus behavior, target delivery, or any side effects of pressing a key.

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 only two sentences, front-loaded with the action and then providing compact, relevant examples. Every word earns its place with no redundancy.

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 simple 2-parameter tool without output schema, the description is mostly adequate, yet it fails to explain the role of the mandatory 'app' parameter. An agent might not understand that the key press is scoped to a particular application or requires that app to be active/focused, leaving a meaningful invocation gap.

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%, so the parameters are already documented. The description adds value above the schema by clarifying the accepted key syntax (xdotool examples) and explicitly naming modifier/navigation keys, making the 'key' parameter more meaningful.

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?

The description states a specific verb and resource: press a key or key-combination on the keyboard. It gives concrete examples ('a', 'Return', 'super+c') that distinguish it from text-typing tools, though it does not explicitly name or contrast sibling tools.

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

Usage Guidelines2/5

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

No guidance is given about when to use this tool versus alternatives like type_text or click. The description implies keyboard-only input but does not state exclusions or provide conditions for choosing this tool.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/tmustier/codex-computer-use-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server