Skip to main content
Glama
petri-net-sim

pns-server MCP Server

add_assembly

Creates a join pattern that synchronizes multiple input flows into one output. Configurable with named slots, weighted inputs, and assembly time.

Instructions

Add an Assembly (Join) pattern that synchronizes multiple flows into one.

Creates one new input place per slot named "{name}In{slot_name}" and a transition that fires when ALL slots have tokens. The caller must wire external sources to those slots via connect_patterns — the slot place_ids are returned in the response and in metadata.

WEIGHTED INPUTS (for multiple tokens required):

  • Simple: inputs=["PartA", "PartB"] - requires 1 token from each

  • Weighted: inputs=[{"name": "Type1", "weight": 10}, {"name": "Type2", "weight": 10}]

Args: name: Name for this assembly (e.g., "CarAssembly", "SectionFill") inputs: Names for the input slots created by this assembly assembly_time: Mean firing time in time_unit distribution: Time distribution priority: Transition priority (higher = fires first in conflict) time_unit: Unit for time values — "s", "min", "h", or "d" (days)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYes
inputsYes
assembly_timeNo
distributionNodet
priorityNo
time_unitNos

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

With no annotations, the description discloses key behaviors: creates input places, transition fires when all slots have tokens, requires external wiring via connect_patterns, and returns slot place_ids. It covers creation and wiring requirements well, though does not discuss auth or rate limits.

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

Conciseness4/5

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

The description is reasonably sized and front-loaded with purpose. It includes examples and details, though there is slight redundancy in explaining weighted inputs. Overall, it is well-structured.

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 6 parameters, no schema coverage, but an output schema exists, the description covers all parameters, use case, wiring, and return behavior. It lacks some specifics on output format but is sufficient for a complex tool.

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 coverage is 0%, but the description compensates fully by explaining each parameter in the Args section, including examples for weighted inputs, defaults, and time units. It adds significant meaning beyond the schema.

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?

The description clearly states that the tool adds an Assembly (Join) pattern that synchronizes multiple flows into one, distinguishing it from siblings like add_fork_join or add_merge. It provides specific verb and resource, and includes examples.

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?

The description implies usage for synchronizing flows but lacks explicit guidance on when to use versus alternatives (e.g., add_fork_join, add_merge). No when-not-to-use or alternative comparison is provided.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/petri-net-sim/pns-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server