Skip to main content
Glama
petri-net-sim

pns-server MCP Server

add_merge

Combine multiple streams into one output with a Merge pattern. Fires when any input has a token, useful for funneling orders from web, phone, fax into one processing queue.

Instructions

Add a Merge (OR-join / Funnel) pattern — combines multiple streams into one output.

Fires as soon as ANY input has a token (unlike Assembly which waits for ALL). Creates one input place per stream named "{name}In{stream_name}". Wire each producer's output into the corresponding place via connect_patterns.

Use this for:

  • Orders from web, phone and fax all going to one processing queue

  • Parts from parallel machines going to one inspection station

Args: name: Name for this merge point (e.g., "OrderMerge") inputs: Stream names (e.g., ["Web", "Phone", "Fax"])

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYes
inputsYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

Despite no annotations, the description reveals important behaviors: creates one input place per stream with naming convention, and instructs to wire via connect_patterns. Could add more about side effects like place creation, but sufficient.

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

Conciseness5/5

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

Very concise: three sentences plus a bulleted use-case list and parameter descriptions. No extraneous information.

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?

Complete for an add tool: explains creation of places, wiring, and gives examples. Output schema exists, so return values are covered.

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?

Both parameters are explained with examples (name as 'OrderMerge', inputs as array of stream names). Schema has no descriptions, so the tool description fully compensates.

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 it adds a merge pattern (OR-join) that combines multiple streams into one output, with a specific verb and resource. It distinguishes from assembly by noting it fires on ANY input, not ALL.

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

Usage Guidelines5/5

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

Provides explicit when-to-use: orders from multiple sources to one queue, parts from parallel machines. Also contrasts with assembly tool, giving clear differentiation.

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