FlexSim MCP Server

Overview Schema Source Related Servers Discussions Admin

flexsim_inspect_model

Inspect a FlexSim model to list all objects with properties, connections, resources, and stats as JSON, plus simulation time and Student license warnings.

Instructions

List every object of the model in the FlexSim window as JSON (window backend).

For each object: name, class, position [x, y, z], `to` (flow connections), `resources` (resource
connections such as an Operator) and, for Source/Queue/Processor/Sink/Combiner/Separator/MultiProcessor,
`stats` {input, output, content_avg, content_max}. Also returns the simulation time.

Student (100 objetos, docs oficiales FlexSim): si count>=85 agrega `license_hint` # CNT-limite
"85+/100 objetos (límite licencia Student; ver GUIA)"; si count>100 informa igual # CNT-limite
(la ventana lo permite abrir pero FlexSim bloquea). # CNT-limite

Input Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

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.7/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 it does add real behavioral context: the per-object payload shape, which classes carry `stats`, that simulation time is returned, and especially the Student-license count thresholds (85+/100) that trigger a `license_hint`. It omits safety/profile traits (read-only, prerequisites), keeping it short of a 5.

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 core purpose is front-loaded and the field list is useful, but the Student-license block is cluttered with inline '# CNT-limite' markers and mixed-language commentary that add noise without much clarity.

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?

An output schema exists, so return values need not be spelled out, and the description still covers payload shape, the license behavior, and the returned simulation time. Nothing critical for calling a zero-parameter read tool 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?

The tool takes zero parameters, so the baseline of 4 applies; the description correctly adds no parameter guidance because none is needed.

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 ('List every object of the model... as JSON') and the window-backend scope. It is distinguishable from read-oriented siblings like flexsim_list_tree or flexsim_get_statistics by its whole-model object dump, but it never names those alternatives 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?

The parenthetical '(window backend)' implies the operating context but gives no explicit when-to-use or when-not-to-use guidance relative to siblings such as flexsim_list_tree or flexsim_get_statistics. Usage is only loosely implied.

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

Deploy Server