Skip to main content
Glama
RapidMiner / Altair AI Studio MCP

RapidMiner / Altair AI Studio MCP

rm_status

Retrieve AI Studio version, process location, run state, operator and problem counts, and perspective to monitor and troubleshoot active workflows.

Instructions

AI Studio version, current process location, run state, operator/problem counts, perspective.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.8/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 of behavioral disclosure. It reveals which fields come back but says nothing about whether the call is read-only, whether it fails when no process is loaded, or what happens in a disconnected state.

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?

It is a single short fragment with zero wasted words, which is good, but the verbless comma list makes it under-structured rather than crisply front-loaded. Adding a lead-in such as 'Returns...' would cost one word and gain clarity.

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?

There is no output schema, so the description is the only place return values can be sketched, and it lists four content areas without types, formats, or ordering. For a parameterless status tool this is roughly adequate but thin, and it omits any dependency on connection/process state.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool takes zero parameters, so the baseline of 4 applies; no parameter semantics are needed and none are missing.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description is a noun list ('AI Studio version, current process location, run state, operator/problem counts, perspective') with no verb, so it reads as a summary of return contents rather than a statement of what the tool does. It is inferable that this is a status snapshot of the Studio/process, but nothing distinguishes it from adjacent tools like rm_operator_info or rm_process_structure.

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 when-to-use guidance, no mention of prerequisites (e.g. needing rm_connect or a loaded process first), and no routing to sibling tools. The only implicit signal is that it yields a general status summary.

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