Skip to main content
Glama
RapidMiner / Altair AI Studio MCP

RapidMiner / Altair AI Studio MCP

rm_select

Selects combo box, list, table, tree, or tab pane items by visible text or item index; supports tree paths and double-click to open or activate the chosen item.

Instructions

Select an item in a combo box, list, table, tree or tab pane by text (or item_index). For trees, value can be a path 'Samples > data > Iris'. double_click=true opens/activates it.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "rm_select"
  }
}

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
exactNoExact (not substring) text match
indexNoWhich match to use when several match (0-based)
valueNo
windowNoWindow id from rm_windows (default: active window)
tooltipNoMatch tooltip text
item_indexNo
double_clickNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations, the description carries the full burden, and it does disclose meaningful behavior: double_click=true opens/activates instead of merely selecting, and tree values use a ' > ' path separator. It does not say what happens when no item matches, whether multiple matches error out, whether the item is scrolled into view, or what the call returns.

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?

Two compact sentences, front-loaded with the primary action and followed by the two special cases that matter most (tree path and double_click). It is dense but readable; the parenthetical '(or item_index)' interrupts the opening sentence slightly but doesn't waste space.

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, zero-annotation, no-output-schema tool, the description covers the core selection workflow and the two notable special cases, but leaves failure behavior, multi-match semantics, and half a dozen matcher parameters to the schema. It is adequate but not complete for a tool with this much surface area.

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 73%, so most parameters are already documented, and the description adds real meaning for two of them: item_index as an alternative to text selection and value as a tree path. It says nothing about the distinct 'index' (which match to use) versus 'item_index' (position within the item list) distinction, nor about exact/class/tooltip matching, leaving the most confusion-prone parameters unexplained.

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 gives a specific verb ('select') plus a concrete resource set ('item in a combo box, list, table, tree or tab pane'), which is far more informative than the bare name rm_select. It doesn't explicitly contrast with the nearby rm_click or rm_operator_select siblings, so an agent must infer that this tool targets item collections rather than arbitrary clicks.

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 through the selector mode ('by text (or item_index)') and the tree-path example, which tells an agent how to address nested items. However, there is no explicit when-to-use guidance, no statement of when to prefer rm_click or rm_operator_select, and no prerequisites or constraints.

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