Skip to main content
Glama
RapidMiner / Altair AI Studio MCP

RapidMiner / Altair AI Studio MCP

rm_settings_get

Read Altair AI Studio preferences by key to retrieve a single value, or filter preference keys to list matching settings.

Instructions

Read AI Studio preferences (Settings > Preferences). Give key for one value, or filter to list matching keys.

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

Input Schema

NameRequiredDescriptionDefault
keyNo
filterNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.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 behavioral burden. "Read" implies a safe non-mutating call, but there is nothing on what the response looks like (single value vs. key list), whether missing keys error or return empty, or any permission/availability considerations.

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?

Two sentences, no filler, with purpose stated before parameter guidance. It could be marginally tighter, but every clause carries information an agent needs.

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 two-parameter read tool with no output schema and no annotations, the definition covers the selection logic but leaves the return shape vague (does a filter listing include values or only keys?). Adequate but not fully self-sufficient.

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%, so the description must compensate, and it does define the intent of both parameters: key targets one value, filter lists matching keys. However, the matching syntax for filter (substring, glob, regex?) and the behavior when both parameters are present remain undocumented.

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?

"Read AI Studio preferences (Settings > Preferences)" gives a specific verb plus resource and even locates it in the UI, which cleanly separates it from the sibling rm_settings_set. It stops short of explicitly naming the write counterpart, but the read-only framing is unmistakable.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The second sentence is an explicit mode selector: pass key to fetch a single value, or use filter to list matching keys. That resolves the main usage ambiguity for callers. It does not state what happens when both are supplied or when neither is supplied, which is the remaining gap.

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