Skip to main content
Glama
RapidMiner / Altair AI Studio MCP

RapidMiner / Altair AI Studio MCP

rm_process_save

Save the current RapidMiner process to its existing location or to a new .rmp file path, preserving your process design changes for later reuse.

Instructions

Save the current process (to its location, or to a new .rmp path).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "rm_process_save"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.1/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden for a write-to-disk operation. It never says what happens with no open process, whether an existing file at the given path is overwritten, whether a save-as becomes the new current location, or what is returned on success/failure.

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 the default behavior before the alternative, and no filler. The parenthetical is slightly compressed in a way that makes it read as one clause where a second short sentence would be clearer.

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 a completely undocumented parameter, the description is thin. An agent cannot tell from it whether saving requires an existing process session or whether the write is destructive to an existing file.

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 description coverage is 0% and the single parameter is an unannotated string, so the description must compensate. It does add real meaning by naming it a '.rmp path' and by marking it optional through the 'to its location, or...' phrasing, but it omits overwrite and path-persistence semantics.

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 ('Save the current process') rather than restating the name, and the parenthetical clarifies the two save modes. It doesn't explicitly contrast with siblings, but none of the listed siblings (open/new/run/stop) overlap in function, so the purpose is readable at a glance.

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?

The parenthetical implies the two calling modes: omit the path to save in place, supply one to save to a new .rmp location. There is no statement of preconditions (a process must already be new/open) or of when-not to use it, so usage is only implied.

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