FlexSim MCP Server

Overview Schema Source Related Servers Discussions Admin

flexsim_disconnect_objects

Disconnect two FlexSim objects by removing flow output-to-input or resource central links, and optionally verify the post-disconnect state.

Instructions

Disconnect two objects (window backend only).

Uses contextdragconnection with the DISCONNECT keys from the official command
reference (FlexSim 2026 help/CommandReference/Commands.xml, defaultdragconnection
entry): 'Q' disconnects output->input ports (flow), 'W' disconnects central
ports (resource). There is NO objectdisconnect command in FlexSim 2026 (verified
in Commands.xml and live: it returns 0 and changes nothing).
NOTE: connects ACCUMULATE (each connect adds a parallel link), so disconnect
all matches before reconnecting.
flow verifica que target ya no esta en outObjects de source; resource verifica
que target ya no esta en centerObjects de source. Devuelve OK/FAIL con estado post.

Args:
    source: origin (or requester for resource).
    target: destination (or resource for resource).
    kind: flow or resource.
    verify: check outObjects (flow) or centerObjects (resource).

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.7/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 so well: it discloses the underlying command path, keyed behavior per port type ('Q' flow, 'W' resource), the accumulation caveat for connects, and the OK/FAIL outcome. Missing only permission/auth requirements, but behavioral disclosure is otherwise strong.

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?

Front-loaded and informative, but oversized: the mechanism history and the Spanish sentence partially duplicate the English verify explanation, and the language switches mid-description. Sentences mostly earn their place but trimming and language consistency would help.

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-value detail is optional, yet the description still notes the OK/FAIL post-state. Combined with the mechanism, port-type keys, and caveats, it is complete enough for an agent to call a window-backend disconnect correctly.

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: the Args block defines source, target, kind (flow/resource), and verify (check outObjects for flow, centerObjects for resource). It adds real meaning beyond the schema's bare property names and pattern.

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+resource ('Disconnect two objects') and pins down the mechanism ('window backend only', contextdragconnection). It is clearly distinguishable from the inverse flexsim_connect_objects, though it never names that sibling explicitly. Purpose is unambiguous.

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?

Gives useful context (no objectdisconnect command exists in FlexSim 2026; use DISCONNECT keys) and a caveat-driven instruction ('disconnect all matches before reconnecting'). However it never states an explicit when-to-use vs alternative or a clean set of conditions/exclusions, so guidance is implied rather than stated.

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

Deploy Server