Skip to main content
Glama
RapidMiner / Altair AI Studio MCP

RapidMiner / Altair AI Studio MCP

rm_ui_get

Retrieves full details for one UI component: its text and rows, items, or tabs for tables, lists, trees, combos, and tabs. Use it to inspect a component by id or matcher.

Instructions

Details of one component: full text, and for tables/lists/trees/combos/tabs their rows/items/tabs.

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_ui_get"
  }
}

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)
windowNoWindow id from rm_windows (default: active window)
tooltipNoMatch tooltip text
max_rowsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/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. It usefully discloses the return content, including full text and rows/items/tabs for container-like components, but does not state that this is a read-only operation, whether it mutates state, or what happens when multiple matches exist.

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?

The description is a single front-loaded sentence with no filler. The trailing enumeration of component types is compact, though slightly cryptic without punctuation around the list.

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 a nine-parameter lookup tool with no output schema, the description gives a reasonable account of what comes back, including the special rows/items/tabs content for certain component types.

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 description coverage is 89%, so the schema already documents match fields such as name, text, class, tooltip, index, and window. The description adds little parameter meaning beyond implying that a single component is identified, which is the baseline expectation when the schema is rich.

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: it returns the details of one UI component, including its full text. The phrase 'one component' distinguishes it from tree- or search-oriented siblings such as rm_ui_tree and rm_ui_find, though it never names those alternatives.

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?

There is no explicit guidance on when to use this tool rather than rm_ui_tree or rm_ui_find. The only hint is the implicit notion of fetching one component, leaving the agent to infer the workflow from the schema's 'Component id from rm_ui_tree / rm_ui_find'.

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