Skip to main content
Glama

flexsim_collector_create

Create a Statistics Collector object in FlexSim at a specified name and position, with optional overwrite. Use it to set up statistics collection for simulation models.

Instructions

Create one Statistics Collector object (window backend only).

Camino SEGURO y honesto (ver bloque DB-bind): Object.create + name unico +
setLocation + return verificado (receta de flexsim_dashboard_create,
AGENTE_FLEXSIM.md sec 9). La clase del grupo statistics NO esta verificada
en repo ni Commands.xml (grep 2026-09-26: collector 0 hits), asi que
collector_class es libre (default "StatisticsCollector"): si Object.create
falla se devuelve el error real de FlexSim sin mentir ni inventar clases
candidatas.

Args:
    name: nombre unico (solo letras, digitos, _).
    collector_class: clase libre del grupo statistics (default
        "StatisticsCollector", no verificado).
    x, y, z: posicion en metros (default 0, 0, 0).
    overwrite: si True destruye el objeto previo con el mismo nombre.

Returns JSON {name, class, created} o {name, class, created:false, error}
con el error real + hint para listar candidatas a mano por
flexsim_execute_script con library().find("?statistics").
Limite: solo creacion+posicion verificadas; configuracion interna del
collector no verificada (ver flexsim_collector_record).

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

A4.4/5.0
Behavior5/5

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

With no annotations, the description fully carries the behavioral burden: it discloses Object.create + unique name + setLocation, that overwrite destroys the previous object, that failures return the real FlexSim error without inventing classes, and that collector_class is unverified. This is unusually thorough for a tool with no annotation coverage.

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/Limite structure is helpful. However, the 'Camino SEGURO y honesto' and internal doc references add meta-commentary that does not help an agent invoke the tool correctly, making it longer than necessary.

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?

Despite an output schema existing, the description still clearly explains success/failure returns and the unverified-class limitation. With no annotations and 0% schema coverage, it supplies enough behavioral, parameter, and error-handling context to call the tool correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/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: name is unique and limited to letters/digits/underscore, collector_class is free-form with an unverified default, x/y/z are positions in meters, and overwrite destroys the prior object. It adds meaning well beyond the schema's type/default constraints.

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 one Statistics Collector object (window backend only)'. It points to flexsim_collector_record for internal configuration, distinguishing related tasks, but does not explicitly distinguish itself from the generic flexsim_create_objects sibling.

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?

Provides clear context: window backend only, creation+position verified, internal configuration not verified and referred to flexsim_collector_record. This gives an exclusion and a related alternative, though it never says when to prefer this over flexsim_create_objects.

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