Skip to main content
Glama

flexsim_link_transporter

Link a transporter to a dispatcher via resource (S) connections in FlexSim, with optional processor linking and verification. Use it to set up dispatching relationships.

Instructions

Link a transporter to a dispatcher via resource (S) connections (window backend only).

Cadena minima documentable: contextdragconnection(transporter, dispatcher, "S")
(el transporter pide trabajo al dispatcher, analogo a Processor->Operator
verificado). Si processor dado, ademas contextdragconnection(processor,
dispatcher, "S") con kind resource y verificacion de cada enlace con
centerObjects. Topologia Dispatcher movil no verificada end-to-end
(sin TaskSequence de prueba).

Args:
    dispatcher: dispatcher object name.
    transporter: transporter object name (e.g. TaskExecuter/AGV).
    processor: optional processor linked to the dispatcher as resource.
    verify: check centerObjects (default True).

Returns JSON {links: [{from, to, verified}], warning}.
Warning: topología Dispatcher móvil no verificada end-to-end (sin TaskSequence de prueba).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
paramsYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.3/5.0
Behavior3/5

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

With no annotations provided, the description carries the full behavioral burden. It usefully discloses the window-backend-only restriction, the centerObjects verification behavior, and an important warning about unverified mobile Dispatcher topology, but it does not state permissions, side effects, reversibility, or what happens to existing links.

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 purpose is front-loaded, and the Args/Returns structure is useful. However, the description mixes English and Spanish, includes a code-like implementation chain, and repeats the mobile-Dispatcher warning, which adds redundancy rather than 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?

Given the operation's complexity, the nested input schema, and the existence of an output schema, the description is largely complete: it explains the link target, optional processor behavior, verification, and an important topology warning. The main gap is that it does not route the agent away from sibling linking/connection tools.

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. Its Args section documents all four inner parameters: dispatcher, transporter with examples, optional processor, and verify with its default and centerObjects meaning.

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 description states a specific verb and resource: linking a transporter to a dispatcher via resource (S) connections, with a window-backend-only constraint. It is clear enough to distinguish the operation from generic model manipulation, but it does not explicitly name or differentiate itself from sibling tools such as flexsim_connect_objects or flexsim_attach_resource.

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

Usage Guidelines2/5

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

The description explains mechanics and optional behavior but does not say when to use this tool versus alternatives like flexsim_connect_objects, flexsim_attach_resource, or flexsim_agv_connect. No prerequisites, exclusions, or routing guidance are provided.

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

Deploy Server

Other Tools