FlexSim MCP Server

Overview Schema Source Related Servers Discussions Admin

flexsim_agv_deliver

Deliver one item via an AGV network: dispatch travel-load-travel-unload tasks from pickup to dropoff, then run the simulation and report delivery evidence.

Instructions

Deliver one item on the AGV network: TRAVEL pickup, LOAD, TRAVEL dropoff, UNLOAD + run (window only). # AGV-dlv

Fuente (sin inventar comandos ni task types): createemptytasksequence
(Commands.xml:6854-6858, XML:6855/6858) + inserttask (Commands.xml:7951-7955,
ej. XML:7955 "inserttask(ts, TASKTYPE_TRAVEL, current, NULL);") +
dispatchtasksequence (Commands.xml:7094-7099, ej. XML:7099); TASKTYPE_TRAVEL=8
(a objeto, el de red AGV) vs TRAVELTOLOC=9 (a coordenadas, XML:6921-6927, no red)
en FlexsimDefs.h:215-216 / allobjects.h:295-296 (catalogo AGV-dlv A1 arriba);
TASKTYPE_LOAD en XML:7751, UNLOAD solo en FlexsimDefs.h:210 / allobjects.h:290,
PREEMPT_NOT en FlexsimDefs.h:262. Despacho via _dispatch_trip (A2, misma TS de
flexsim_run_transport bloque P1). Patrones verificados del repo: require_gui /
run_script / fs_string / _fs_literal / check_script_safety / format_error;
NULL-check `treenode n = Model.find(..); return (n == NULL ? 0 : 1);`
(flexsim_experimenter_status); item por paths candidatos tal cual,
pickup/item y scan hijos (flexsim_run_transport); red con _flow_path BFS
outObjects (flexsim_agv_connect/_last_link); stats `Object k = Model.find(..);
return k.stats.input.value;` (AGENTE_FLEXSIM.md sec 7); corrida sin reset con
Run Speed slider + stoptime + applicationcommand run + espera getrunstate==0
(flexsim_run_to_time / flexsim_run_transport, sin resetmodel porque borraria la TS).

Args:
    traveler: TaskExecuter/AGV que ejecuta (dueno de la TS).
    item_from: flowitem a mover (Model.find debe resolverlo; ver items con
        flexsim_list_tree sobre la estacion).
    pickup: objeto/estacion donde se carga.
    dropoff: objeto/estacion donde se descarga (se leen sus stats).
    control_points: 0-6 ControlPoints/path de la red (default []); si no vacia
        se verifica con _flow_path que pickup alcanza el primer CP (reporta,
        no bloquea).
    run_seconds: duracion simulada a correr tras despachar (default 600, >0).
    run_speed: Run Speed slider para la corrida (default 1000, >0).
    priority: prioridad de la TS (default 1).

Returns JSON {dispatched, delivered, traveler, item_from, item_path, pickup,
    dropoff, priority, flexsim_result, dropoff_input_before, dropoff_input_after,
    model_time_end, flexsim_console, network_checked:{...}, limits[]} (+ error
    real cuando dispatched=false o sin confirmar entrega, sin mentir).
Limits: semantica LOAD/UNLOAD (involved1=item, involved2=estacion) no esta en
    Commands.xml (remite al QuickReference); dispatched=true es TS aceptada, no
    entrega; delivered=true es input del dropoff incrementado tras correr
    (evidencia, no trazabilidad del item); network_checked solo reporta.
Presupuesto TE (ajusta el OPERADOR # T5): run_seconds >= distancia_total_m /
    velocidad_TE_mps + 30% margen; velocidad_TE_mps se lee en la GUI del
    TaskExecuter (propiedades del TE), distancia_total_m es el recorrido
    pickup->dropoff por la red AGV.

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

Behavior4/5

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

No annotations are supplied, so the description carries the full burden, and it discloses a lot: 'dispatched=true is TS accepted, not delivery', 'delivered=true is input increment evidence, not item traceability', that the run avoids resetmodel because it would erase the TS, and that network_checked only reports. These are exactly the non-obvious behaviors an agent needs. It loses a point for burying them in dense prose rather than making the operational caveats prominent.

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

Conciseness2/5

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

The core purpose is front-loaded, but the body is bloated with source-code citations (Commands.xml line numbers, FlexsimDefs.h references) and implementation boilerplate that do not help an agent select or invoke the tool. Much of the 'Fuente' paragraph should be stripped; it dilutes the actionable Args/Limits content and mixes languages.

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 complex orchestration tool with no annotations and an output schema present (so return values needn't be re-explained, though the description redundantly lists them), the coverage is strong: params, limits, error semantics, and run behavior are all addressed. It is essentially complete for correct invocation, only hampered by presentation.

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% (only titles and constraints), so the description must compensate, and its Args block documents all eight sub-parameters with meaning — including non-obvious ones like control_points verification via _flow_path and the run_seconds TE budget heuristic. This adds genuine value beyond the bare schema. It is not a 5 because a few entries (e.g. priority) are defined minimally.

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 opening sentence names a specific verb and resource ('Deliver one item on the AGV network') and enumerates the exact task sequence (TRAVEL pickup, LOAD, TRAVEL dropoff, UNLOAD + run), which clearly separates it from lower-level siblings like flexsim_run_transport or flexsim_agv_route. The '(window only)' qualifier further scopes it. It stops just short of 5 because it never explicitly contrasts itself with those siblings by name in a selection-oriented way.

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 rather than stated: it notes the window-backend constraint and points to flexsim_list_tree for discovering items, which helps an agent get set up. However, there is no explicit 'use this instead of X when…' routing or when-not guidance against the many AGV/transport siblings, so the agent must infer the choice.

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

Deploy Server