Skip to main content
Glama
RapidMiner / Altair AI Studio MCP

RapidMiner / Altair AI Studio MCP

rm_log

Retrieve recent RapidMiner/Altair AI Studio or process log lines, filtered by matching text, to inspect execution details and diagnose issues.

Instructions

Recent AI Studio / process log lines (filter with contains).

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

Input Schema

NameRequiredDescriptionDefault
linesNo
containsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.4/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 burden and does little: read-only intent is only implied by 'log lines'. It does not state the default window of lines returned, ordering (newest first?), whether output is truncated, or that filtering is a substring match.

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?

A single short line with no wasted words, but it is a noun phrase fragment rather than a front-loaded statement of action and behavior, and the brevity comes at the cost of the missing parameter meaning.

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

Completeness2/5

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

With no annotations, no output schema, and zero schema description coverage across two parameters, the description is too thin. Critical facts for correct invocation (what 'lines' controls, default quantity, ordering of returned log lines) are absent.

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 0%, so the description must compensate and largely does not. It clarifies that 'contains' is a filter, but never explains that 'lines' bounds how many recent lines are returned or what the default is.

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 names the resource ('Recent AI Studio / process log lines') but omits a verb, leaving the agent to infer that it retrieves/reads log output. It is distinguishable from action siblings like rm_click or rm_process_run, but not clearly separated from result-oriented siblings such as rm_process_results.

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?

The only guidance is the parenthetical '(filter with contains)', which explains one parameter rather than when to choose this tool over alternatives. There is no statement of when log inspection is appropriate versus other process/result tools.

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