Skip to main content
Glama
Sign In
ABB RobotStudio MCP Server

ABB RobotStudio MCP Server

by LiskinLabs
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Local

rs_reset_simulation

Stops the simulation and resets the program pointer to the start position for a fresh simulation run.

Instructions

Reset simulation to start position (stops simulation and resets PP)

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": "rs_reset_simulation"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0

TDQS

A4.2/5.0
Behavior4/5

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

Description discloses that the tool stops simulation and resets PP, providing clear behavioral context beyond the tool name. No annotations exist, so the description carries the full burden and does so adequately for a simple tool.

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?

Single sentence, no unnecessary words. Every part is meaningful and front-loaded.

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?

Tool is simple with no parameters and no output schema. The description adequately explains the action. Missing definition of 'PP' but likely understood in context. Could mention side effects or prerequisites, but not critical.

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?

No parameters exist, so schema coverage is 100%. Description adds no parameter info, which is appropriate since there are none. Baseline score of 4 for zero-parameter tools is justified.

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?

Description clearly states the tool resets simulation to start position, stops simulation, and resets PP. It uses a specific verb and resource, distinguishing it from siblings like rs_start_simulation or rs_stop_simulation.

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 implied by the description, but no explicit guidance on when to use this tool vs alternatives like rs_stop_simulation or rws_reset_pp. The phrase 'reset simulation to start position' suggests a full reset, but no when-not-to-use or alternative mentions.

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