Skip to main content
Glama
RapidMiner / Altair AI Studio MCP

RapidMiner / Altair AI Studio MCP

rm_operator_add

Adds an operator by key to a RapidMiner process or subprocess, optionally setting its name and parameters to build or extend workflows.

Instructions

Add an operator by key (e.g. 'retrieve', 'concurrency:parallel_decision_tree', 'normalize') to the process or into a subprocess of a chain. Optionally name it and set parameters.

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": {
      "key": "<key>"
    },
    "name": "rm_operator_add"
  }
}

Input Schema

NameRequiredDescriptionDefault
keyYes
nameNo
parentNoName of the enclosing operator chain (default: main process)
arrangeNo
parametersNo
subprocessNoSubprocess index in the parent (default 0)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full disclosure burden, yet it says nothing about where in the chain the operator is inserted, what happens if the key is invalid, whether the call is idempotent, or what the response contains. 'Optionally name it and set parameters' hints at mutation side effects but does not describe them.

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 compact sentences with the core action and its examples front-loaded, and no wasted preamble. It is dense but readable; only a slight tightening of the trailing option list would improve it.

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 six-parameter mutation tool with a nested object parameter, no annotations, and no output schema, the description omits the two most consequential behaviors: how insertion position is determined within the chain/subprocess and what the call returns. An agent could call it but not predict its effect on the surrounding process structure.

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 only 33%, so the description must compensate, and it partially does: it clarifies 'key' with concrete examples and explains that name and parameters are optional. However 'arrange' is never mentioned, and 'subprocess' and 'parent' meanings are left entirely to the schema.

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?

States a specific verb and resource ('Add an operator'), gives three concrete example keys ('retrieve', 'concurrency:parallel_decision_tree', 'normalize'), and notes it lands in the process or a subprocess of a chain. This clearly separates it from siblings like rm_operator_remove, rm_operator_rename, or rm_operator_set_parameters, 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 Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no explicit when-to-use or when-not guidance, and no mention of alternatives such as rm_process_new for building a fresh process or rm_operator_set_parameters for tweaking an operator that already exists. The agent must infer usage purely from the verb.

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