Skip to main content
Glama
RapidMiner / Altair AI Studio MCP

RapidMiner / Altair AI Studio MCP

rm_process_run

Executes the current AI Studio process and, by default, waits for completion to return result previews and warnings.

Instructions

Run the current process in AI Studio and (by default) wait for it to finish, returning results previews and warnings.

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

Input Schema

NameRequiredDescriptionDefault
waitNo
max_rowsNo
timeout_secondsNo

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?

No annotations are supplied, so the description carries the full burden. It usefully discloses the default waiting behavior and that results previews and warnings come back, but it says nothing about what happens on timeout, what wait=false does, or whether running a process mutates data.

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?

A single efficient sentence with the default behavior front-loaded and no filler. It is appropriately sized for a simple action tool, though it could spend one more clause on timeout behavior.

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?

With no annotations, no output schema, and zero parameter documentation, the description should do more. It covers the return content at a high level (previews, warnings) but omits timeout/partial-run semantics and what a non-waiting invocation returns.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

All three parameters have 0% schema description coverage, so the description must compensate. The phrase "by default... wait" hints at the wait flag's default, but max_rows and timeout_seconds are entirely unexplained, leaving two of three parameters undocumented anywhere.

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?

Names a specific verb (run) and resource (the current process in AI Studio) and states the default behavior. It implicitly distinguishes itself from rm_process_results and rm_process_stop, though it never names a sibling explicitly.

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 current process" implies a process must already be open or selected, but the description never states that prerequisite nor when to prefer rm_process_results, rm_process_stop, or rm_process_validate instead. Usage is only inferable.

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