Skip to main content
Glama
RapidMiner / Altair AI Studio MCP

RapidMiner / Altair AI Studio MCP

rm_operator_rename

Renames a RapidMiner or Altair AI Studio operator using its current and new names, so process workflows can use clear, updated operator labels.

Instructions

Rename an operator.

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>",
      "new_name": "<new_name>"
    },
    "name": "rm_operator_rename"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYes
new_nameYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.6/5.0
Behavior2/5

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

No annotations are provided, so the description must carry the whole burden of behavioral disclosure, but one short sentence does not do that. It does not say whether the rename updates references elsewhere, whether it can collide with an existing name, what happens if the operator is missing, or what is returned. The word 'Rename' implies a mutation, but no mutability, permission, or side-effect details follow it.

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 padding, but its brevity here reflects under-specification rather than efficiency. Nothing in it is wasted, but too little is said.

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 fully undocumented parameters, the definition leaves the agent missing critical call-time information. Given the complexity of the rename operation in an operator-management API, completing the description would require covering behavior and parameter meaning, and it does neither.

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 neither parameter has a description in the schema, so the description must compensate. 'Rename an operator' weakly frames 'name' as the target and 'new_name' as the replacement, but it never states the expected format, whether the name is a path or an identifier, or what happens on a conflict.

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 ('Rename') and a specific resource ('operator'), so the agent knows exactly what action the tool performs. It does not differentiate this tool from neighbors such as rm_operator_set_parameters or rm_operator_add, which is why it falls short of a 5.

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?

The description gives no guidance about when to use this tool instead of set_parameters, add, or remove. It also does not state prerequisites, such as whether the operator must exist or be selected first.

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