Skip to main content
Glama
RapidMiner / Altair AI Studio MCP

RapidMiner / Altair AI Studio MCP

rm_disconnect

Disconnect a specified port from a RapidMiner operator to remove unwanted process connections and keep workflow structure clean.

Instructions

Disconnect a port.

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": {
      "operator": "<operator>",
      "port": "<port>"
    },
    "name": "rm_disconnect"
  }
}

Input Schema

NameRequiredDescriptionDefault
portYes
operatorYes
directionNo
subprocessNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.2/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, yet it discloses nothing about side effects, whether disconnection is reversible, what happens to the operator/subprocess state, or error conditions. Only the bare mutating verb hints at behavior.

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?

The single sentence is front-loaded and free of waste, but its brevity reflects under-specification rather than efficiency; it provides no structure beyond the verb phrase.

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 mutating tool with four undocumented parameters, no annotations, and no output schema, the description is far too thin. At minimum it should explain the port/operator model and the direction and subprocess parameters.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% across four parameters, and the description explains only "port" implicitly. The required "operator" parameter, the "direction" enum (input/output), and "subprocess" are entirely undefined, leaving an agent unable to populate them correctly.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

"Disconnect a port" names a specific verb and resource, so the basic action is identifiable. However, "port" is never defined (a process connection port vs. a network port), and the definition does not distinguish this from the sibling rm_connect beyond the obvious opposite verb.

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 disconnect versus using rm_arrange or rschema edits, no prerequisites, and no mention of the related rm_connect sibling. An agent must infer the entire usage context 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.