Skip to main content
Glama
RapidMiner / Altair AI Studio MCP

RapidMiner / Altair AI Studio MCP

rm_operator_set_parameters

Configure RapidMiner operator parameters by name using key-value pairs with string-encoded values, enabling process setup and execution control.

Instructions

Set operator parameters, e.g. {"criterion":"gain_ratio","maximal_depth":"10"}. List/enum parameters use RapidMiner's string encoding (see rm_process_xml for examples).

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": {
      "name": "<name>",
      "parameters": "<parameters>"
    },
    "name": "rm_operator_set_parameters"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYes
parametersYes

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?

With no annotations, the description carries the full burden of behavioral disclosure and does not say whether this requires an existing operator, whether unspecified parameters are preserved, whether the change persists to the process, or what errors occur on unknown parameter names. It does add genuine value by explaining that list/enum values use RapidMiner's string encoding, but the mutation semantics remain opaque.

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 encoding caveat; nothing is wasted. It is perhaps over-terse for a mutation tool, but it is not padded.

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 mutable, nested-object tool with zero annotation and zero schema description coverage and no output schema, the description is thin: prerequisites, side effects, and how to learn valid parameter names are all absent. The encoding note and example help but do not close the gap.

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 0%, so the description must compensate; the inline example {"criterion":"gain_ratio","maximal_depth":"10"} does clarify that the nested parameters object maps parameter names to string-valued settings, which is meaningful. However, the required "name" parameter (presumably the target operator) is never explained, and valid parameter names are not discoverable from the 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?

States a specific verb and resource ("Set operator parameters") which is immediately identifiable as a mutation of a named operator's configuration. It does not distinguish itself from siblings like rm_operator_get or rm_settings_set, but the core action is unambiguous.

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 guidance on when to use this versus alternatives such as rm_process_set_xml or rm_operator_add, nor any stated prerequisites (e.g., that the operator must already exist in the process). The only cross-reference, rm_process_xml, is offered for encoding examples rather than for choosing between tools.

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