Skip to main content
Glama
RapidMiner / Altair AI Studio MCP

RapidMiner / Altair AI Studio MCP

rm_operator_info

Retrieve full documentation for a RapidMiner operator key, including description, parameters with types, defaults and ranges, input and output ports, and subprocesses.

Instructions

Documentation of an operator key: description, all parameters (type, default, range), ports, subprocesses.

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": {
      "key": "<key>"
    },
    "name": "rm_operator_info"
  }
}

Input Schema

NameRequiredDescriptionDefault
keyYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.3/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It does disclose what the result contains (parameters with defaults and ranges, ports, subprocesses), which is genuinely useful in the absence of an output schema, but it omits whether the call is read-only, what happens for an unknown key, and any error behavior.

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?

A single compact sentence that front-loads the resource and then lists the returned fields in order of importance. Nothing is redundant or padded.

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 simple one-parameter read tool this is close to adequate, and enumerating return contents substitutes for the missing output schema. However, with no annotations and no parameter documentation, the description should have stated that it is a non-mutating lookup and how an unknown key is handled.

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 coverage is 0% for the single 'key' parameter, so the description must compensate. It clarifies that the key identifies an operator, but gives no format, naming convention, or existence requirement, leaving the parameter only partially specified.

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 concrete resource (an operator key) and enumerates the documentation it surfaces: description, parameters with type/default/range, ports, subprocesses. The agent knows this is a read of operator metadata, but the description does not distinguish it from the sibling rm_operator_get, which likely retrieves overlapping data.

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?

No when-to-use guidance, no mention of when to prefer rm_operator_get or rm_operator_search, and no prerequisites such as whether the operator must already exist or be added. The agent must infer the usage context entirely.

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