Skip to main content
Glama
Sign In
ABB RobotStudio MCP Server

ABB RobotStudio MCP Server

by LiskinLabs
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Local

rs_read_variable

Read the initial value of a RAPID variable in an ABB robot task. Provide the task and variable name to retrieve the value.

Instructions

Read a RAPID variable initial value (SDK)

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": {
      "task": "<task>",
      "name": "<name>"
    },
    "name": "rs_read_variable"
  }
}

Input Schema

NameRequiredDescriptionDefault
taskYes
nameYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0

TDQS

C2.4/5.0
Behavior2/5

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

No annotations provided, so the description must disclose behavior. It states 'read' implying no side effects, but fails to specify error conditions (e.g., variable not found), whether the robot must be in a certain state, or if it requires connection to a real controller.

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?

The description is very concise (single sentence), but it omits critical information. It is not front-loaded with the most important details beyond the basic action.

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?

Given two required parameters, no output schema, and no annotations, the description is too minimal. It does not explain the return value, potential errors, or any constraints, leaving the agent underinformed.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema has 0% description coverage, and the description does not explain the meaning of 'task' and 'name'. These are likely the RAPID task name and variable name, but the description offers no clarification, leaving the agent to guess.

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 clearly states 'Read a RAPID variable initial value (SDK)', indicating a read operation on a specific resource. It distinguishes from sibling tools like rs_write_variable (write) and rs_list_variables (list). However, the phrase 'initial value' could be more precise, but overall the purpose is clear.

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 like rs_list_variables or rs_read_variable (RWS version). No mention of when not to use it or any preconditions.

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