Reads the full RAPID source code of a specified module so you can inspect or edit its logic during RobotStudio station work.
Read full RAPID source code of a module (SDK)
| Name | Required | Description | Default |
|---|---|---|---|
| task | Yes | ||
| module | Yes | e.g. 'module_MAIN', 'module_EGM', 'Wizard_Params' |
Changes observed during successful MCP inspections.
v3.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are present, so the description must carry full behavioral disclosure. It states it reads 'full RAPID source code' but does not mention if it requires special permissions, the scope of the data returned, or any side effects. This is insufficient for a read tool.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single sentence that is concise but lacks structure. It does not include headings, bullet points, or any organization that would aid quick comprehension.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the absence of an output schema and the generic sibling set, the description should explain what 'full source code' means, the format of the output, and any constraints (e.g., module must exist). The current description is too minimal to be complete.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Only one parameter ('module') has a description with examples, which adds useful context. The 'task' parameter lacks any description, leaving its meaning unclear. With 50% schema coverage, the description partially compensates but does not fully clarify semantics.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the action ('Read full RAPID source code') and the resource ('module'), making the tool's purpose evident. However, it does not differentiate from siblings like 'rs_read_module' vs 'rws_read_module', which may cause confusion.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
No guidance is provided on when to use this tool versus alternatives such as 'rs_write_module' or 'rws_read_module'. The description lacks context about prerequisites or typical use cases.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.