Skip to main content
Glama
RapidMiner / Altair AI Studio MCP

RapidMiner / Altair AI Studio MCP

rm_operator_enable

Toggle an operator's enabled state in RapidMiner or Altair AI Studio by specifying its name and boolean value, so processes can include or bypass operators.

Instructions

Enable or disable an operator.

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

Input Schema

NameRequiredDescriptionDefault
nameYes
enabledYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.6/5.0
Behavior2/5

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

No annotations are supplied, so the description bears the full behavioral burden and falls short. It does not say whether the state change persists across sessions, whether disabling affects a currently running process, what happens if the operator name is unknown, or what the call returns. For a mutation tool with zero annotation coverage this is a significant gap.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single short sentence with no wasted words, but the brevity comes at the cost of under-specification rather than efficiency. Nothing is front-loaded beyond the bare purpose.

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 mutation tool with no annotations, no output schema, and two undocumented parameters, the description does far too little. An agent would have to guess at identifier format, side effects, and outcome reporting.

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% with two required parameters. The description never explains that 'name' is the operator identifier (and in what form it should be supplied) or how 'enabled' interacts with the tool's dual enable/disable purpose. It adds no meaning beyond the bare property names.

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: it toggles an operator's enabled state. An agent can tell it apart from add/remove/rename siblings by the enable/disable framing, though the name (rm_operator_enable) only names half the behavior. The description is clear but does not differentiate further from rm_operator_set_parameters, which could plausibly overlap.

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?

No when-to-use guidance, no prerequisites (e.g., the operator must already exist, typically discovered via rm_operator_get or rm_operator_search), and no alternatives named such as rm_operator_set_parameters. The 'disable' variant being folded into an 'enable'-named tool is never explained.

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