FlexSim MCP Server

Overview Schema Source Related Servers Discussions Admin

flexsim_set_distribution

Sets a time property distribution (exponential, uniform, normal, constant) on a FlexSim object for window backend models. Use it to configure inter-arrival or similar timing properties.

Instructions

Set a time property distribution by read-modify-rewrite (window backend only).

Verified: exponential par2 (media) via ", <viejo>/**/" mold replace + constant
via setProperty(number) (AGENTE_FLEXSIM.md sec 6). uniform/normal rewrite the
two tagged numbers ONLY when the current code already is that distribution.
CHANGING FAMILY (exponential->uniform/normal) IS REFUSED: the 2026 mold has
par1..par5 slots and a renamed mold leaves par4/par5 empty
(uniform(2,8,stream,,)), which CRASHED FlexSim live (2026-09-26 probe6:
process gone during the next run). Change family by hand in the GUI or use
constant. The stream argument is accepted but the original stream expression
is preserved (third param untouched).

The uniform/normal/exponential (y constant) output reports expected_mean
(exponential=par2, uniform=(par1+par2)/2, normal=par1, constant=valor)
para contraste humano.

Functional check (humano): flexsim_reset + flexsim_run_to_time hasta T +
leer Source.stats.output (arrivals) y contrastar arrivals ~= T / expected_mean
(p. ej. T=600, mean=5 -> ~120 llegadas; tolerancia por variabilidad aleatoria).

Args:
    object: object name (e.g. Source1).
    property: property name (default InterArrivalTime).
    distribution: exponential, uniform, normal or constant.
    par1: uniform min / normal mean / constant value (when par1 set).
    par2: exponential mean / uniform max / normal std / constant value (fallback).
    stream: accepted for API completeness, preserved as-is (not rewritten).

Limits: only the standard mold with /**/ tags is rewritten; a mold
    without tags returns an error (no fallback to constant, no corruption).
    Family changes (exponential->uniform/normal) are refused: they crashed
    FlexSim live (empty par4/par5 slots). Change family in the GUI or use
    constant.

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.2/5.0

Behavior5/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 so richly: it discloses a live FlexSim crash on family change (with date and probe id), the exact failure mode (empty par4/par5 slots), error behavior for tag-less molds (no fallback, no corruption), and stream-preservation semantics. It also documents the expected_mean output for human contrast.

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

Conciseness3/5

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

The first sentence is well front-loaded, but the body is verbose, mixes English and Spanish ('para contraste humano'), and repeats the family-change refusal in both the main text and the Limits section. The embedded functional-check recipe for humans adds bulk without helping tool selection.

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?

For a mutation tool with real crash risk and a tag-based rewrite constraint, the description is thorough enough to call it safely, and it even explains return semantics despite an output schema existing. Nothing an agent needs to avoid the documented failure modes is missing.

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: par1/par2 are defined per distribution, the par2 fallback for constant is noted, and stream is explained as accepted-but-preserved. Minor residual ambiguity remains around par1 vs par2 for constant and the bare 'object: object name'.

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 ('Set a time property distribution') plus the mechanism (read-modify-rewrite, window backend only), which is more than a name restatement. It does not, however, explicitly contrast itself with the nearest siblings such as flexsim_set_parameter or flexsim_set_node_value, leaving that routing to the agent.

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?

Gives clear operating context (window backend only) and concrete exclusions: family changes are refused, tag-less molds error, and the stream argument is ignored. It names workarounds (change family in the GUI or use constant). It stops short of stating when to prefer a sibling tool, so it is clear context without full alternative routing.

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

Deploy Server