Skip to main content
Glama
RapidMiner / Altair AI Studio MCP

RapidMiner / Altair AI Studio MCP

rm_operator_select

Selects an operator in the RapidMiner GUI and displays it so its parameters appear in the Parameters panel for configuration.

Instructions

Select an operator in the GUI and show it (its parameters appear in the Parameters panel).

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>"
    },
    "name": "rm_operator_select"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3/5.0
Behavior3/5

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

With no annotations, the description carries the full burden, and it does disclose one useful behavioral fact: selection changes the GUI state so the operator's parameters show in the Parameters panel. It does not say what happens if the name is not found, whether a process must be open, or whether prior selection state is lost.

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?

One sentence with the action and its effect front-loaded and no filler. It is short rather than padded, though the parenthetical could have been spent on a prerequisite instead.

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 one-parameter GUI action with no output schema and no annotations, the description covers what the tool does and one side effect. Missing are prerequisites (open process/window), error behavior for an unknown operator, and any note on return value, which an agent would need before calling.

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?

The single required parameter 'name' has 0% schema description coverage, and the description only implies it identifies 'an operator' — it never clarifies whether this is a display name, a unique path, or an ID, nor whether it is case-sensitive. The description does not compensate for the schema gap.

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 (Select) and resource (an operator in the GUI), plus the observable effect that its parameters appear in the Parameters panel. It is distinguishable from rm_operator_get (retrieve data) and rm_operator_set_parameters (modify), though it does not explicitly disambiguate against the generic rm_select sibling.

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-to-use guidance, and no named alternative such as rm_select or rm_operator_get. The GUI-select context is implied only by the word 'GUI' and the mention of the Parameters panel.

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