Skip to main content
Glama
RapidMiner / Altair AI Studio MCP

RapidMiner / Altair AI Studio MCP

rm_operator_remove

Delete an operator from a RapidMiner process by name to remove unwanted steps and keep process workflows clean and accurate.

Instructions

Delete an operator from 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_remove"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.7/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 behavioral burden for a destructive operation. It does not state whether deletion is permanent or undoable, what happens to the operator's connections, whether an open process is required, or what occurs if the name does not exist. Only the scope ('from the process') adds anything.

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 front-loaded sentence with zero filler; the verb and object come first. It is efficient, though its brevity reflects under-specification rather than disciplined minimalism.

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 destructive one-parameter mutation tool with no annotations and no output schema, the description says almost nothing beyond the operation's name. An agent lacks enough information to call it safely or to predict the result of a name that does not match any operator.

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, so the description must compensate — but it never mentions the parameter at all. It does not say whether 'name' is a display name, internal ID, or path, nor anything about case sensitivity or uniqueness within the process.

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 uses a specific verb plus resource plus scope: 'Delete an operator from the process.' That cleanly separates it from siblings like rm_operator_add, rm_operator_enable, and rm_operator_rename. It does not explicitly name an alternative, but the operation itself 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 rm_operator_select, rm_operator_set_parameters, or rm_operator_add, and no prerequisites such as whether the process must be open or the operator selected first. The agent must infer usage solely from the tool name and the word 'Delete.'

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