LucidFlow BPMN validator

Validate a BPMN 2.0 file

validate_bpmn

Read-onlyIdempotent

Checks a BPMN 2.0 XML file against the LucidFlow validator rules and returns the errors and warnings with their locations. Free, no account, nothing is stored. Limits: 200 KB, 1500 elements, 50 levels deep, no DOCTYPE, 2 seconds. Rate: 60 calls per minute and 1000 per day per IP address; a BPMN XML file of more than 100 KB counts for 5 calls.

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": {
      "xml": "<xml>"
    },
    "name": "validate_bpmn"
  }
}

Input Schema

Name	Required	Description	Default
`xml`	Yes	The BPMN 2.0 XML text (not a URL).

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 13, 2026

TDQS

A4.5/5.0

Behavior5/5

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

Annotations already declare read-only, idempotent, non-destructive and closed-world, and the description adds genuinely new behavior: no account required, nothing persisted, hard input limits, a 2-second execution cap, and concrete rate limits (60/min, 1000/day per IP, with >100 KB counting as 5 calls). That is exactly the operational detail an agent cannot get from the annotations.

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?

Two sentences: the first front-loads purpose and return value, the second packs all limits and quota rules into a compact list. No filler or repetition.

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?

With no output schema, the description still explains the return content (errors and warnings with locations), and it covers every constraint that could cause a call to fail. For a one-parameter validator this is fully sufficient.

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?

The single parameter has 100% schema coverage, including maxLength 204800 and the 'not a URL' clarification, so the schema does the heavy lifting. The description restates the 200 KB ceiling consistent with maxLength but adds no new meaning about the xml field itself, which matches the baseline for fully documented parameters.

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?

States a specific verb (checks/validates) and resource (a BPMN 2.0 XML file), names the rule set (LucidFlow validator), and says what comes back (errors and warnings with locations). Nothing about the tool's function is left to inference.

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 size, element, depth, DOCTYPE and timeout limits effectively tell an agent when this tool is and isn't usable, and the no-account/no-storage framing clarifies the context. There are no sibling tools to route against and no explicit 'when not to use' beyond the hard limits, so it stops short of a 5.

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

All LucidFlow BPMN validator tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?