Skip to main content
Glama
RapidMiner / Altair AI Studio MCP

RapidMiner / Altair AI Studio MCP

rm_process_structure

Inspect the current RapidMiner/Altair AI Studio process as a readable outline, including operators, non-default parameters, connections, problems, and nested subprocesses.

Instructions

Readable outline of the current process: operators (name [key]), non-default parameters, connections, problems, nested subprocesses.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

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 disclosure burden. It implies a read-only inspection ('Readable outline'), but says nothing about prerequisites (an open process), whether the output is text or structured, how large processes are handled, or whether the read has any side effects — significant gaps for a tool with zero annotation coverage.

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 colon-fronted sentence with a compact enumerated list — nothing is redundant, and the key scoping word ('current process') leads the description. Every item in the list conveys distinct output content.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema and no parameters, the description is the sole source of return-value information, and it enumerates the sections of the outline well. What's missing is the counterpart relationship to rm_process_xml and the precondition that a process must be loaded, which would make it fully self-sufficient.

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 no parameters, so by baseline this scores 4. The description correctly adds no parameter prose and instead spends its words on scope and content, which is the right allocation for a zero-argument tool.

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 names the resource (the current process) and precisely enumerates what the outline contains: operators with name and key, non-default parameters, connections, problems, and nested subprocesses. 'Readable' signals a summarized, human-oriented view rather than raw markup, though it never explicitly names rm_process_xml as the machine-readable counterpart.

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 explicit when-to-use or when-not-to-use guidance and no sibling is named as an alternative. An agent must infer from the implicit 'current process' context that a process must already be open, and must guess how this differs from rm_process_xml or rm_process_validate.

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