motionworks-iec-mcp-server

Overview Schema Source Related Servers Discussions Admin

open_project

Open a MotionWorks IEC project, detect its source format, merge all exports, and return a summary with divergences. For native projects without exports, it provides export guidance.

Instructions

Open a MotionWorks IEC project, merging every export form present.

This is the entry point for every other tool. path may be a PLCopen XML file, an Extended IEC 61131-2 export directory, or a native project directory — the source is detected, not declared.

Returns the project summary plus a divergences list. Read that list: the exports are incomplete in different ways (an XML export can omit POUs that the Extended export has, or ship them with an empty body), so a divergence is often the most important thing about a project.

If you passed a native project (.mwt) with no export beside it, the response also carries an exportGuidance block. Its code lives in a compound binary, so no source, variables, types or I/O can be read. The block says exactly what is missing, what that costs you, the verbatim steps to produce each export, and — if exports exist elsewhere on disk — the path to the one matching this project. Relay those steps to the user rather than guessing at the code.

Args: path: File or directory to open.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`path`	Yes

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Sep 27, 2026

TDQS

A5/5.0

Behavior5/5

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

With no annotations, the description fully discloses behavioral traits. It explains that exports are merged and divergences are returned, highlighting that divergences are often the most important aspect. For native projects, it states that code lives in a compound binary, so no source, variables, types, or I/O can be read, and it provides exportGuidance with detailed instructions. This is exemplary transparency.

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 well-structured with the main purpose front-loaded, followed by essential behavioral details and special-case handling. While longer than some, every paragraph adds critical information for correct invocation and interpretation. It is appropriately sized for a complex entry-point tool.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The description covers what the tool does, what it returns (summary and divergences), how to interpret the divergences, and the special native-project scenario with exportGuidance. Given the complexity and the presence of an output schema, this is complete enough for an agent to use it correctly without further information.

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

Parameters5/5

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

Despite schema description coverage being 0%, the description thoroughly explains the 'path' parameter by enumerating the three accepted formats (PLCopen XML, Extended IEC export directory, native project directory) and noting that the source is auto-detected. This adds significant meaning beyond the schema's bare string type.

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 tool opens a MotionWorks IEC project and merges all export forms. It identifies itself as the entry point for every other tool, distinguishing it from siblings like load_project. The verb, resource, and scope are explicit, and the path type detection is described.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description explicitly states it is the entry point for every other tool, giving strong guidance on when to use it. It also explains the accepted path types and the special case for native projects with no export, including how to handle exportGuidance. This is clear, actionable usage guidance.

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