Skip to main content
Glama
Sign In
ABB RobotStudio MCP Server

ABB RobotStudio MCP Server

by LiskinLabs
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Local

rs_get_modules

Retrieve a list of all RAPID modules from a specified task in RobotStudio. Provide a task name to get modules for inspection or programming.

Instructions

List RAPID modules in a task (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": "rs_get_modules"
  }
}

Input Schema

NameRequiredDescriptionDefault
taskYesTask name, e.g. 'T_ROB1'

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0

TDQS

A3.5/5.0
Behavior2/5

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

No annotations are provided, so the description must bear the full burden. It offers no insights into side effects, permissions, error handling, or output format beyond the basic listing.

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, complete sentence with no wasted words, perfectly sized for the tool's simplicity.

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?

Given no output schema and no annotations, the description is minimally adequate for a simple list operation but lacks details on return value format and behavior when task is invalid.

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% with a description for the single parameter 'task' (e.g., 'T_ROB1'). The description adds no additional semantics beyond the example, so stays at baseline.

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 clearly states the verb 'List' and the resource 'RAPID modules in a task', with context 'SDK'. It distinguishes from sibling tools like rs_read_module and rws_get_modules.

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?

The description implies SDK usage via parentheses but provides no explicit when-to-use or when-not-to-use guidance against siblings like rws_get_modules.

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