Skip to main content
Glama
RapidMiner / Altair AI Studio MCP

RapidMiner / Altair AI Studio MCP

rm_process_open

Opens a RapidMiner .rmp process file from disk for inspection and editing in Altair AI Studio.

Instructions

Open a .rmp process file from disk.

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": {
      "path": "<path>"
    },
    "name": "rm_process_open"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathYes

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?

With no annotations, the description carries the full behavioral burden but only says the file comes "from disk." It does not disclose whether opening replaces or closes the current process, whether unsaved changes are discarded, what errors occur on a missing or invalid file, or whether the operation is read-only versus state-changing.

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 short sentence with the verb and resource front-loaded and no filler. It is efficient, though the brevity comes at the cost of the missing detail noted elsewhere rather than being a model of economy.

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 state-mutating load operation with no annotations, no output schema, and an undocumented parameter, the description is too thin. An agent cannot tell what happens to the currently loaded process, what a successful open returns, or how failures manifest.

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% and the single `path` parameter has no documented format in either the schema or the description. The description only implies the path points to a .rmp file on the local filesystem, leaving absolute vs. relative path, extension handling, and encoding unaddressed.

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 states a specific verb ("Open") and a specific resource (a .rmp process file), which lets an agent distinguish it from siblings like rm_process_new (create) and rm_process_save (persist). It stops short of naming any sibling 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 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_process_new, rm_process_run, or rm_process_results, and no stated prerequisites such as whether the file must exist or whether an already-open process is replaced. The only implied context is that a .rmp file on disk is the input.

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