Skip to main content
Glama
RapidMiner / Altair AI Studio MCP

RapidMiner / Altair AI Studio MCP

rm_process_results

Retrieves the results of the last RapidMiner process run, showing each result port's type and a data preview with rows, columns, or text.

Instructions

Results of the last run: each result port's type plus a data preview (rows/columns) or text.

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

Input Schema

NameRequiredDescriptionDefault
max_rowsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior3/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 does disclose the return shape — per-port type plus either a tabular preview or text — which is genuinely useful, but it says nothing about behavior when no run has occurred, whether the preview is truncated, or whether the call is side-effect free.

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?

One tight sentence with no filler, and the core noun ('Results of the last run') is front-loaded. It is efficient but slightly clipped, reading as a return-value fragment rather than a complete statement of what the tool does.

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 and no annotations, the description is the only source of return-value information, and it covers the shape reasonably (port type, tabular preview, or text). It still leaves gaps on error/empty-run behavior and on the sole parameter, which matter for a tool whose entire purpose is returning data.

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?

The single parameter max_rows has 0% schema description coverage, and the description never mentions it. The reference to a 'data preview (rows/columns)' hints that output size is limited, but the agent cannot learn from the description whether max_rows caps preview rows, what the default is, or what happens if it is omitted.

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 a specific resource: the results of the last process run, broken down per result port as a type plus a data preview (rows/columns) or text. That clearly distinguishes it from rm_process_run (which executes) and rm_process_log, though it never states a verb or names a sibling explicitly.

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?

Usage is only implied by the phrase 'last run' — an agent can infer it should be called after executing a process, but the description never says so, gives no prerequisites (e.g., that a run must exist first), and names no alternative tool for retrieving results.

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