Skip to main content
Glama
Sign In
ABB RobotStudio MCP Server

ABB RobotStudio MCP Server

by LiskinLabs
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Local

rs_set_sim_speed

Sets the simulation speed multiplier to control the pace of robot operations in the virtual environment.

Instructions

Set simulation speed multiplier

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": {
      "speed": "<speed>"
    },
    "name": "rs_set_sim_speed"
  }
}

Input Schema

NameRequiredDescriptionDefault
speedYesSpeed multiplier (1.0 = normal)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0

TDQS

B3.2/5.0
Behavior2/5

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

No annotations are provided, so the description carries full burden. The description does not disclose behavioral traits such as whether the change is immediate, persistent, or requires a restart. For a mutation tool, this is insufficient.

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?

The description is a single, concise sentence with no superfluous words. It is front-loaded and directly states the purpose.

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?

For a simple setter tool, the description should contextualize the effect (e.g., immediate, global to simulation). Lacking any context about side effects or state dependencies, it feels incomplete.

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 100%, and the description adds no additional meaning beyond what the schema already provides for the 'speed' parameter. Baseline of 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description 'Set simulation speed multiplier' clearly states the action (set) and the resource (simulation speed multiplier). It is specific and unambiguous, and it distinguishes itself from sibling tools like 'rs_pause_simulation' or 'rws_set_speed_override' which target different aspects.

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 guidance on when to use this tool versus alternatives. It does not mention prerequisites (e.g., simulation must be running), nor does it provide any conditions or exclusions. The agent is left with no decision support beyond the basic purpose.

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

Deploy Server

Other Tools