Skip to main content
Glama
RapidMiner / Altair AI Studio MCP

RapidMiner / Altair AI Studio MCP

rm_process_set_xml

Replace the current RapidMiner process with XML from a .rmp file to build a complete process from an existing definition.

Instructions

Replace the current process with the given process XML (as in a .rmp file). Fastest way to build a whole 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": {
      "xml": "<xml>"
    },
    "name": "rm_process_set_xml"
  }
}

Input Schema

NameRequiredDescriptionDefault
xmlYes
keep_locationNoKeep the current file location (default true)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/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; it does disclose the key trait that the existing process is replaced, which implies destruction of current content. It says nothing about unsaved-change loss, validation failures on malformed XML, or whether the tool errors versus silently producing a partial process.

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

Conciseness5/5

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

Two short sentences, front-loaded with the action and resource, then a single use-case rationale. No filler or restatement of the tool name.

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 2-parameter, annotation-free mutation tool with no output schema, the description covers the core intent and the file-format hint. It omits the destructive side effects (existing process and unsaved edits), error behavior on invalid XML, and any indication of what the call returns.

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

Parameters3/5

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

Schema coverage is 50%: keep_location is documented in the schema, while xml has no schema description. The description partially compensates by clarifying the XML format ('as in a .rmp file'), which is genuine added meaning the schema lacks, but it says nothing about the required-ness or size/shape of that payload.

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 ('Replace the current process') plus the input form ('given process XML'), which separates it from read/open-style siblings like rm_process_xml or rm_process_open. It never names an alternative explicitly, so differentiation is inferred rather than stated.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

'Fastest way to build a whole process' gives an implied selection rationale versus assembling operators one by one. There is no explicit when-not guidance, no mention of when rm_process_open or rm_process_new would be preferable, and no prerequisites such as whether the current process must be stopped first.

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