FlexSim MCP Server

Overview Schema Source Related Servers Discussions Admin

flexsim_ensure_parameter

Ensure a FlexSim model parameter exists, creating it if missing or updating its value if present. Works only on window backend.

Instructions

Ensure a model parameter exists, creating it when missing (window backend only).

Replicates the VERIFIED pattern of AGENTE_FLEXSIM.md sec 3c over
Tools/ParameterTables/Parameters>variables/parameters: Table addRow +
cell(k,1).value=name + cell(k,2).value=value. When the parameter already
exists (Model.parameters.names() contains it) only the value is updated.
Returns JSON {name, created, value, backend}. Validates rectangular
scalar values and types (number|string). Never touches
PerformanceMeasureTables.

Args:
    name: Parameter name (only letters, digits, _).
    value: New value (number or string, must match type).
    type: number (default) or string.

Limits: needs the Toolbox ParameterTables node in the model; string cells
    with '|' or ';' are stored verbatim (no split here, unlike table_read).

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

Behavior4/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 well: it discloses the create-vs-update branching (Model.parameters.names() check), the returned JSON shape, type/rectangular validation, and the limit that string cells with '|' or ';' are stored verbatim. It omits permission/auth needs and reversibility, but is otherwise unusually thorough.

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?

Purpose is front-loaded, but the implementation-detail sentence ('Replicates the VERIFIED pattern of AGENTE_FLEXSIM.md sec 3c ... Table addRow + cell(k,1).value=name ...') is largely internal mechanics that doesn't help an agent select or invoke the tool, adding bloat.

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?

Covers backend restriction, prerequisite node, validation, and the PerformanceMeasureTables exclusion, which is sufficient for correct invocation. An output schema exists so return-value detail is a bonus rather than a requirement, and the description supplies it anyway.

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 via an Args block: name charset, value as number|string that 'must match type', and type defaulting to number. This adds a meaningful cross-field constraint ('must match type') the schema does not express.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb+resource with scope: 'Ensure a model parameter exists, creating it when missing (window backend only).' The create-or-update semantics distinguish it from the read/write siblings flexsim_get_parameter and flexsim_set_parameter without opening either schema.

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 context: window backend only, requires the Toolbox ParameterTables node, and updates value when the parameter already exists. However, it never explicitly routes the agent away from flexsim_set_parameter or states a 'when not to use' condition.

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

Deploy Server