Skip to main content
Glama
petri-net-sim

pns-server MCP Server

add_priority_choice

Create a priority choice pattern: primary transition fires if resources available, else alternative transition executes.

Instructions

Add a PriorityChoice pattern for resource-dependent branching.

Implements "do X if resources available, otherwise do Y" logic. Primary transition has higher priority and fires first if resources available.

Args: name: Name for this choice point (e.g., "SectionFill") resource_place_ids: Resource requirements for primary path. Each dict: {"place_id": "p5", "weight": 10} primary_delay: Delay for primary/success transition in time_unit alternative_delay: Delay for alternative/fallback transition in time_unit primary_name: Name suffix for success output alternative_name: Name suffix for fallback output time_unit: Unit for time values — "s", "min", "h", or "d" (days)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYes
resource_place_idsNo
primary_delayNo
alternative_delayNo
primary_nameNoSuccess
alternative_nameNoFallback
time_unitNos

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior3/5

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

With no annotations, the description bears the full burden. It describes the logic (primary transition fires first if resources) and the meaning of parameters, but lacks details on side effects, permissions, or limitations. Adequate but not comprehensive.

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 concise at around 10 lines, starting with a clear purpose then an overview and a parameter list. Front-loaded and efficient, though the parameter descriptions could be slightly more streamlined.

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 7 parameters (1 required), no schema descriptions, and an output schema (so return values are covered externally), the description adequately explains the tool's purpose, behavior, and all parameters. It is complete enough for an agent to use 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 coverage is 0%, so the description must compensate. It provides detailed explanations for all 7 parameters, including the format for resource_place_ids and the time_unit options, adding significant value over the bare 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 it adds a 'PriorityChoice pattern for resource-dependent branching' with a specific logic ('do X if resources available, otherwise do Y'). This distinguishes it from sibling tools that add other patterns.

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?

The description explains when to use this tool (resource-dependent branching) and describes the behavior, but it does not explicitly list when not to use it or name specific alternatives, though the sibling list implies alternatives.

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