Skip to main content
Glama
RapidMiner / Altair AI Studio MCP

RapidMiner / Altair AI Studio MCP

rm_operator_get

Retrieve an operator’s parameters—values, defaults, and ranges—and its port connections to inspect and configure a RapidMiner process.

Instructions

All parameters (value/default/range) and port connections of an operator in the process.

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

Input Schema

NameRequiredDescriptionDefault
nameYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.1/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 behavioral burden. It does disclose the shape of the returned data (parameter values, defaults, ranges, and port connections), which is genuinely useful with no output schema, but it never states that the call is read-only, what happens when the name does not resolve, or whether an open process is required.

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 compact sentence with no filler; the returned content is front-loaded. The telegraphic noun-phrase style costs a little clarity compared with an explicit verb, but nothing is wasted.

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

Completeness4/5

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

For a one-parameter read tool with no output schema and no annotations, the description covers the essential question of what comes back. The remaining gaps are the meaning of the 'name' argument and failure/selection preconditions, which keep it short of fully self-sufficient.

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?

Schema description coverage is 0% for the single required 'name' parameter, and the description never mentions it explicitly. 'Of an operator' weakly implies the argument identifies the operator, but it does not clarify whether that is an operator name, a path, an ID, or a currently selected operator, nor whether name matching is exact.

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 the resource (an operator in the process) and specifies exactly what is retrieved: all parameters with value/default/range plus port connections. That is more specific than a bare 'get operator', though it is phrased as a noun fragment with no explicit verb and does not distinguish it from the similarly named rm_operator_info 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 guidance on when to use this instead of rm_operator_search, rm_operator_info, or rm_operator_set_parameters, and no preconditions such as whether the operator must be selected or loaded in an open process. The agent must infer the use case from the name alone.

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