Skip to main content
Glama
RapidMiner / Altair AI Studio MCP

RapidMiner / Altair AI Studio MCP

rm_type

Types text into a target or focused text field, with options to replace existing content and press Enter after input.

Instructions

Type value into a text field (found by target query, or the focused one). clear=true replaces the content; enter=true presses Enter after.

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": {
      "value": "<value>"
    },
    "name": "rm_type"
  }
}

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.9/5.0
Behavior4/5

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

No annotations are supplied, so the description carries the full disclosure burden and does add real behavior: clear=true replaces existing content, enter=true submits with a keypress. Gaps remain — it never says what happens if the target is not a text field, if nothing matches, or whether the field must already be focused.

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 compact sentences, the primary action first, then the two modifier flags. No filler or repetition of schema text.

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?

For an 11-parameter tool the description covers the action, the target-lookup concept, and the two non-obvious flags, while the schema documents the selector parameters. No output schema exists, so the missing detail on failure behavior is the main residual 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 82%, so the baseline is 3; the description goes beyond it by giving meaning to the two bare booleans `clear` and `enter`, which have no schema description at all. It does not touch the selector parameters, but the schema documents those already.

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 concrete verb and resource: 'Type `value` into a text field', plus how the field is located ('found by target query, or the focused one'). That is specific enough to distinguish it from click/scroll/select siblings, though no sibling is named as an explicit alternative.

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 phrasing (enter text into a field), and the fallback to the focused field is a useful contextual hint. There is no explicit when-to-use versus when-not guidance, e.g. no note on using rm_key for key presses or rm_click to focus a field first.

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