Skip to main content
Glama
RapidMiner / Altair AI Studio MCP

RapidMiner / Altair AI Studio MCP

rm_ui_find

Locate UI components across all open windows by text, name, tooltip, or Java class, then retrieve their IDs and screen positions for inspection or automation.

Instructions

Find components on all windows by text/name/tooltip/class. Returns ids and positions.

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

Input Schema

NameRequiredDescriptionDefault
nameNoMatch Swing component name
textNoMatch visible text / label (substring, case-insensitive)
classNoMatch Java class name, e.g. JButton, JTree
exactNoExact (not substring) text match
limitNo
tooltipNoMatch tooltip text

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.3/5.0
Behavior3/5

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

With no annotations, the description carries the behavioral burden. It usefully discloses scope (all windows) and return content (ids and positions), but omits whether the operation is read-only, what happens when nothing matches, and how the limit parameter affects behavior.

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 tightly written sentences with zero waste. The purpose and scope are front-loaded, and the return value is stated immediately after.

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 a six-parameter search tool with no output schema and no annotations, the description is adequate but thin. It covers match fields and return shape, but leaves the limit parameter, no-match behavior, and relationship to sibling tools unexplained.

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 83%, so the schema already documents most parameters, including substring/case-insensitive matching and the exact flag. The description names the match fields but adds no syntax or behavior beyond what the schema provides, making the baseline 3 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?

The description uses a specific verb ("Find") and resource ("components on all windows") and enumerates the matching criteria (text/name/tooltip/class). It is immediately clear what the tool does, though it does not explicitly differentiate itself from siblings like rm_ui_tree or rm_ui_get.

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 guidance on when to use this tool versus alternatives. The agent must infer that this is a search step preceding rm_click or rm_ui_get, and there is no mention of when not to use it or how it relates to rm_ui_tree.

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