Skip to main content
Glama
RapidMiner / Altair AI Studio MCP

RapidMiner / Altair AI Studio MCP

rm_ui_tree

Dumps a window's Swing component tree or a subtree by component ID, listing IDs, classes, text, names, tips, and bounds; use interactive_only to reduce noise.

Instructions

Dump the Swing component tree of a window (or a subtree via id). Each line: [id] Class "text" name= tip= @x,y wxh (window coords). Use interactive_only to cut noise.

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

Input Schema

NameRequiredDescriptionDefault
idNoStart at this component instead of the whole window
windowNoWindow id from rm_windows (default: active window)
max_depthNo
max_nodesNo
interactive_onlyNo

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, and it does disclose the output line format — a genuinely useful behavioral detail an agent cannot get from structured fields. However, it says nothing about read-only nature explicitly, truncation behavior when max_depth/max_nodes are hit, or the cost of dumping a large tree.

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?

Three short sentences, front-loaded with what the tool does, followed by the output shape and a noise-reduction tip. The line-format template is terse but dense with information; no filler.

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 zero-annotation, no-output-schema tool the output format disclosure goes a long way, but the absence of any explanation for max_depth/max_nodes and of truncation or size-limit behavior leaves real gaps for an agent planning a large dump.

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 40%, and the description covers only id ("subtree via id"), window ("of a window"), and interactive_only. The two undocumented parameters, max_depth and max_nodes, are not mentioned at all, leaving traversal-cost control unexplained in both schema and description.

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?

"Dump the Swing component tree of a window (or a subtree via id)" gives a specific verb and resource with the scoping options named. It is clear what the tool returns, though it does not explicitly distinguish itself from structural siblings like rm_ui_find 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?

The only usage-adjacent sentence is "Use interactive_only to cut noise," which is a parameter tip rather than a when-to-use rule. Nothing says when to reach for a full tree dump versus targeted lookup tools, or when a window-level dump is too broad.

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