Skip to main content
Glama
RapidMiner / Altair AI Studio MCP

RapidMiner / Altair AI Studio MCP

rm_connect

Connects an operator output port to another operator input port in RapidMiner / Altair AI Studio processes, including subprocess inner ports, so data flows correctly.

Instructions

Connect an output port to an input port. Use 'Process:inner' (or 'process') / ':inner' for a subprocess's inner ports, e.g. connect 'Decision Tree'.'model' -> 'Process:inner'.'result 1'.

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": {
      "from_operator": "<from_operator>",
      "from_port": "<from_port>",
      "to_operator": "<to_operator>",
      "to_port": "<to_port>"
    },
    "name": "rm_connect"
  }
}

Input Schema

NameRequiredDescriptionDefault
replaceNo
to_portYes
from_portYes
subprocessNo
to_operatorYes
from_operatorYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.1/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden. It never says whether an existing connection on the target input port is overwritten, what the `replace` flag does, whether the process must be open or running, or what happens on failure; only the port-address syntax is disclosed.

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 sentences, front-loaded with the action and followed by the one non-obvious detail plus a concrete example. The quoting in the example is slightly noisy but nothing is wasted.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 6-parameter mutation tool with no annotations, no port-format schema help, and no output schema, the definition is thin. The port-addressing example is valuable, but replacement/overwrite behavior, the subprocess parameter, and preconditions are all missing.

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 0% across 6 parameters, so the description must compensate. It does explain the tricky part — the 'Process:inner' / '<Chain>:inner' string format for from_port and to_port — but leaves `replace` and `subprocess` entirely unexplained and gives no format hints for from_operator/to_operator beyond the example.

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 names a specific verb and resource: connect an output port to an input port. That is unambiguous and implicitly contrasts with rm_disconnect, though no sibling is named 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?

Usage is implied by the tool's nature, and the description does supply the key addressing convention for subprocess inner ports. It gives no preconditions such as requiring an open process or existing operators, and no when-to-use/when-not guidance relative to rm_disconnect or rm_operator_add.

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