Skip to main content
Glama
RapidMiner / Altair AI Studio MCP

RapidMiner / Altair AI Studio MCP

rm_menu

Invoke a main-menu item by path to automate IDE actions, or list available menus and shortcuts when no path is given.

Instructions

Invoke a main-menu item by path, e.g. 'File > Save Process as' or 'View > Restore Default View'. Without path, lists the menus with shortcuts.

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_menu"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathNo
depthNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.3/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. It reveals that paths trigger real menu actions (e.g., 'Save Process as', which mutates state) and that omitting the path changes the behavior to enumeration, but it says nothing about failure modes for a non-existent path, whether the menu must already be open, or what is returned.

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 tight sentences: the primary action and its path syntax come first, with the no-path enumeration mode as a secondary clause. The two inline examples earn their place by encoding the separator format, and there is no filler.

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?

With no output schema the description need not explain returns, and the path format is covered adequately for a 2-parameter tool. The undocumented `depth` parameter and the absence of any error/edge-case behavior leave it only minimally complete.

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%, so the description must compensate; it does document the critical ' > ' separator convention for `path` with two concrete examples. The `depth` parameter is never mentioned anywhere, leaving half the parameters unexplained.

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 ('Invoke') plus the resource ('main-menu item') and clarifies the unit of work is a menu path rather than a raw click, which distinguishes it in practice from siblings like rm_click or rm_key. It does not explicitly name an alternative sibling, so it stops 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 Guidelines3/5

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

The second sentence does describe a second mode ('Without path, lists the menus with shortcuts'), which is real usage guidance for discovery. However, it never says when to prefer this tool over rm_click/rm_key or what to do when a path is invalid, so the guidance is implied rather than explicit.

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