Skip to main content
Glama
RapidMiner / Altair AI Studio MCP

RapidMiner / Altair AI Studio MCP

rm_groovy

Run a Groovy script inside Altair AI Studio with full API access to automate IDE actions, build processes, and return results. Use bound variables for the main frame, process, and output.

Instructions

Escape hatch: run a Groovy script inside AI Studio with full API access. Bound vars: mainFrame (com.rapidminer.gui.MainFrame), process (com.rapidminer.Process), out (PrintWriter). Returns the script result.

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": {
      "script": "<script>"
    },
    "name": "rm_groovy"
  }
}

Input Schema

NameRequiredDescriptionDefault
on_edtNoRun on the Swing UI thread (default true)
scriptYes
timeout_secondsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/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 burden, and it does disclose the execution environment: bound variables mainFrame, process and out, plus that the script result is returned. It falls short on risk profile—nothing about what arbitrary API access can destroy, permission requirements, or what happens on timeout failure.

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 short sentences, front-loaded with the escape-hatch framing before the environment details. Dense and mostly waste-free; only the return statement is mildly redundant with the environment sentence.

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 high-power arbitrary-code tool with no annotations and no output schema, the description covers environment and return but omits timeout behavior, error handling, and the safety implications of "full API access". Adequate but with clear gaps an agent would want before invoking it.

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 only 33%, with script and timeout_seconds undocumented in the schema, so the description partially compensates by explaining the variables available inside the script (mainFrame, process, out). timeout_seconds semantics and units, and the script's return-value expectation, remain unexplained.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ("run a Groovy script inside AI Studio") plus a framing ("escape hatch: full API access") that clearly separates it from the narrow purpose-built rm_* siblings such as rm_operator_set_parameters or rm_click.

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?

The word "escape hatch" plus "full API access" implies this is the fallback when no dedicated tool covers the need, but there is no explicit when-to-use/when-not statement and no named alternative. The agent must infer the routing rule from the label alone.

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