Skip to main content
Glama
RapidMiner / Altair AI Studio MCP

RapidMiner / Altair AI Studio MCP

rm_key

Presses a key or key chord (e.g., ENTER, TAB, ctrl+S) on the focused UI component or a specified target, enabling keyboard-driven interaction and shortcut automation.

Instructions

Press a key or chord on the focused component (or target): e.g. ENTER, ESCAPE, TAB, DELETE, F11, ctrl+S, ctrl+shift+Z.

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

Input Schema

NameRequiredDescriptionDefault
idNoComponent id from rm_ui_tree / rm_ui_find
keysYes
nameNoMatch Swing component name
textNoMatch visible text / label (substring, case-insensitive)
classNoMatch Java class name, e.g. JButton, JTree
exactNoExact (not substring) text match
indexNoWhich match to use when several match (0-based)
repeatNo
windowNoWindow id from rm_windows (default: active window)
tooltipNoMatch tooltip text
wait_msNo

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 supplied, so the description carries the full behavioral burden, yet it only discloses chord syntax via examples. It does not say what happens when no component matches, whether the call blocks or waits for the UI to process, how modifier chords are parsed, or what an error looks like.

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?

A single front-loaded sentence with no filler; the key examples earn their place by fixing the input format. The parenthetical 'or target' is slightly cryptic without naming which targeting parameters it refers to.

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 an 11-parameter keyboard-automation tool with no annotations and no output schema, the definition covers the essentials of what to send and where, but leaves the timing/retry parameters and failure behavior undocumented, which an agent needs to invoke it reliably.

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?

The description adds real value for the required 'keys' parameter, which has no schema description at all, by demonstrating the chord/modifier format. It gestures at the targeting parameters with 'or target' but leaves repeat and wait_ms entirely unexplained; with 73% schema coverage the baseline of 3 is appropriate.

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 specific verb ('press a key or chord') and the resource it acts on ('the focused component (or target)'), backed by concrete key examples like ENTER, ctrl+S, ctrl+shift+Z. An agent can tell this is keyboard input rather than pointer input, though no sibling is named for contrast.

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 rather than stated: 'on the focused component (or target)' hints that omitting a target sends the key to whatever currently has focus, and that targeting is possible. It never says when to prefer this over a sibling like rm_click, nor any preconditions such as a window needing focus.

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