FlexSim MCP Server

Overview Schema Source Related Servers Discussions Admin

flexsim_clone_model

Clone or clear a FlexSim model file to a new destination, optionally opening the copy in FlexSim to start from an existing model or template.

Instructions

Clone the current model file or clear back to the GUI template.

clone: save the window (when connected), copy _gui_model_path or _current_model
    (source_path only when no known origin) to dest_path.
clear: copy the GUI template to dest_path (like flexsim_prepare_gui_model).
With open_in_gui, the copy is opened in FlexSim like flexsim_prepare_gui_model.

Args:
    dest_path: new .fsm file (must not exist, never the template).
    source_path: optional existing .fsm used only when no known origin.
    mode: clone or clear (default clone).
    open_in_gui: open the copy in FlexSim (default True).

Input Schema

TableJSON Schema

Name	Required	Description	Default
`params`	Yes

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Oct 5, 2026

TDQS

A4/5.0

Behavior4/5

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

With no annotations, the description carries the full burden and does well: it discloses the copy semantics, that the window is saved when connected, that dest_path must not exist and can never be the template, and that open_in_gui opens the copy in FlexSim. It stops short of stating permission/auth requirements or what happens to an existing file, but the mutation side effects are clearly conveyed.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The purpose is front-loaded in the first sentence, followed by mode-specific detail and an Args block. It is appropriately sized, though the flexsim_prepare_gui_model comparison is repeated in two places, a minor redundancy.

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?

Given an output schema exists, return values need not be explained, and the description covers modes, all parameters, and file/GUI side effects adequately. It omits auth/prerequisite context, but for a clone/clear operation the coverage is close to complete.

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?

Schema description coverage is 0%, so the description must compensate, and it does: each of the four sub-parameters (dest_path, source_path, mode, open_in_gui) gets an explicit meaning plus constraints and defaults. This is materially more than the bare schema provides. It lacks format examples for paths, keeping it from a 5.

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 first sentence gives a specific verb+resource ('Clone the current model file or clear back to the GUI template') and immediately distinguishes the two modes. It names the related sibling flexsim_prepare_gui_model, so an agent can separate it from other model tools. Slightly tangled by the branching modes, but the core purpose is unambiguous.

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

Usage Guidelines4/5

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

It states the condition that selects each mode (clone vs clear) and clarifies when source_path applies ('only when no known origin'). It references flexsim_prepare_gui_model for the open_in_gui behavior, giving a comparison point. However, it does not explicitly contrast with flexsim_new_model or flexsim_save_model_as, so the routing is not fully closed.

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

Deploy Server