Skip to main content
Glama

rex_send_keys

Send keystrokes such as Ctrl+C or Enter to a terminal session, enabling you to interrupt processes or respond to interactive prompts.

Instructions

Press keys in a terminal (rex send-key), e.g. ["ctrl+c"] or ["enter"].

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

Input Schema

NameRequiredDescriptionDefault
keysYes
blockNoBlock label, ID, or ID suffix
sessionNoSession label or ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior2/5

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

No annotations are provided, so the description must carry the full behavioral burden. It states the action and examples but does not disclose whether keys are sent to the active session or a specified block/session, how errors surface, or whether execution blocks or returns immediately.

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 front-loaded sentence with concrete examples and no redundant wording. It is appropriately sized for a simple action tool.

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 action tool with no annotations and no output schema, the description is incomplete. It omits target-selection semantics, side effects, and execution behavior, leaving the examples as the main operational guidance.

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 coverage is 67%, with block and session already described in the schema. The description adds useful example format for the required keys array, but does not explain block versus session targeting or key-name syntax beyond the two examples.

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 keys in a terminal,' and gives examples such as ["ctrl+c"] or ["enter"]. It does not explicitly distinguish itself from the sibling rex_send_text, though the key-vs-text distinction is implied by the wording.

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 implied by the terminal context and key examples, but there is no explicit guidance on when to use this tool versus alternatives like rex_send_text. No exclusion or prerequisite guidance is provided.

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