Skip to main content
Glama
RapidMiner / Altair AI Studio MCP

RapidMiner / Altair AI Studio MCP

rm_window

Controls an AI Studio window by bringing it to the front, maximizing or resizing it, or closing it with an explicit window ID to manage the interface during automation.

Instructions

Window actions: front, close (like clicking X; needs an explicit window id), maximize, resize.

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": {
      "action": "<action>"
    },
    "name": "rm_window"
  }
}

Input Schema

NameRequiredDescriptionDefault
widthNo
actionYes
heightNo
windowNoWindow id from rm_windows (default: active window)
confirm_exitNoRequired to close the main window (exits AI Studio)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3/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 burden. It does disclose that close terminates the window, which is valuable, but says nothing about resize needing width/height, whether maximize is reversible, or that closing the main window requires confirm_exit (that only appears in the schema).

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 compact sentence that front-loads the action list and attaches the most important caveat (explicit window id for close) inline. No wasted wording, though the parenthetical is a bit dense.

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 five-parameter, unannotated tool with no output schema, the description covers the action space adequately but omits the resize dimension parameters and the destructive-exit confirmation, leaving meaningful gaps an agent would only discover in the schema.

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 only 40%, so the description must compensate. It only explains the window-id requirement for close; width, height, and confirm_exit semantics are left entirely to the schema, and the resize dimensions are never mentioned in prose.

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 clear resource (window) and enumerates the four supported actions: front, close, maximize, resize. An agent can distinguish this from siblings like rm_arrange or rm_click, though nothing explicitly contrasts their roles.

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 clarifies that close behaves like clicking X and requires an explicit window id, which is a useful usage prerequisite. However, there is no guidance on when to pick this tool over rm_arrange or which action values pair with which parameters.

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