MCP-BPMN Server

by oisee

Overview Schema Source Related Servers Discussions Admin

TypeScript

Local

add_lane

Add a lane to an existing pool in a BPMN diagram by specifying the pool ID, lane name, and optional position.

Instructions

Add a lane to an existing pool in the current diagram

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "poolId": "<poolId>",
      "name": "<name>"
    },
    "name": "add_lane"
  }
}

Input Schema

Name	Required	Description	Default
`name`	Yes	Name of the lane
`poolId`	Yes	ID of the pool to add lane to
`position`	No	Position relative to existing lanes	bottom

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.2.0Jul 30, 2026

TDQS

A3.5/5.0

Behavior2/5

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

No annotations are provided, so the description carries the burden of behavioral disclosure. It only states the basic action without revealing side effects, required context (e.g., pool must exist), or response behavior.

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?

The description is a single concise sentence, front-loaded with the action and object, containing no unnecessary words.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple tool with full schema coverage and no output schema, the description minimally covers the purpose but lacks completeness on conditions like pool existence or position semantics.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3. The description adds no extra meaning beyond the schema's parameter descriptions.

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 the verb 'Add' and the resource 'lane to an existing pool in the current diagram', distinguishing it from siblings like add_pool that add pools instead.

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 adding lanes to existing pools but provides no explicit guidance on when to use versus alternatives, nor any conditions or prerequisites.

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