FlexSim MCP Server

by FelipeDiazAimar

Overview Schema Source Related Servers Discussions Admin

Python

Local

flexsim_new_model

Create a new FlexSim model when no blank-model command exists: copy the bridge template to a new .fsm file and open it.

Instructions

Create a new model from the bridge template and open it.

FlexSim has no script command to create a blank model, so this copies the template
(config.toml [bridge] template_model, which already contains the bridge node) to a new
.fsm file and opens it.

Args:
    model_path: Path of the new .fsm file (must not exist yet)

Example:
    model_path="C:/Models/warehouse.fsm"

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

A3.8/5.0

Behavior4/5

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

No annotations are provided, so the description carries the full burden and does so reasonably: it discloses the write side effect (a new .fsm file is created on disk), that the model is opened, and the precondition that model_path 'must not exist yet.' It omits error behavior (e.g., missing directory, existing file) and any permission requirements.

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?

Front-loads the action in the first sentence, then explains rationale and args in clearly separated blocks. The config.toml parenthetical is a touch verbose but earns its place by explaining the template source.

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?

For a single-parameter creation tool with an output schema, the description covers purpose, mechanism, the parameter constraint, and returns are handled by the output schema. Only edge-case/error behavior is left unstated, which is a minor gap.

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. It identifies model_path as the path of the new .fsm file and adds a critical constraint ('must not exist yet') not present in the schema, plus a concrete example value. This meaningfully exceeds the bare schema.

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?

States a specific verb and resource ('Create a new model from the bridge template') and discloses the mechanism (copies the template to a new .fsm and opens it). An agent can tell this creates-from-template rather than opening (flexsim_open_model) or cloning (flexsim_clone_model), though no sibling is named explicitly.

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?

Usage is implied through the constraint that 'FlexSim has no script command to create a blank model,' which explains why this tool exists. However, it never states when to prefer it over flexsim_open_model or flexsim_clone_model, nor any explicit when-not guidance.

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

Deploy Server