Skip to main content
Glama

cmmn-create_sentry

cmmn-create_sentry

Create a CMMN Sentry to guard case item activation or completion using event triggers, multiple conditions, and evaluation modes.

Instructions

Creates a CMMN Sentry with optional CMMN 1.1 enhancements (multiple conditions, evaluation modes).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
case_idYesCase ID (@rid format)
conditionNoCondition expression or description for AI to evaluate
condition_logicNoHow to combine conditions: 'and' (all) or 'or' (any)
condition_typeNoHow to interpret condition: expression or description
conditionsNoArray of conditions: [{source_ref, event, condition, logic}] for complex sentries
descriptionNoDetailed explanation of the criterion
evaluation_modeNoonPart (remember satisfied parts - default) or onEvent (re-evaluate each time)
exit_typeNoFor exit sentries: 'exit' (abort), 'complete' (success), 'forceComplete' (force)
guards_itemNoItem ID this sentry guards (task, stage, milestone)
nameYesSentry name/description
parent_idNoParent item ID (for hierarchical nesting)
requiredNoIs this sentry required for parent stage auto-complete? Default: true
sentry_typeYesType: entry (guards activation) or exit (guards completion)
source_refNoItem ID to watch for events (e.g., task that must complete)
standard_eventNoEvent that triggers evaluation: complete, terminate, create, update, delete, occur
Behavior2/5

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

No annotations are provided, so the description bears full responsibility. It only mentions 'enhancements' without disclosing behavioral traits like idempotency, permissions, error handling, or side effects such as overwriting existing sentries.

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 a single, concise sentence that conveys the core purpose without redundancy. It could be slightly expanded for clarity, but it is appropriately front-loaded and efficient.

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

Completeness2/5

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

Given 15 parameters, no output schema, and no annotations, the description is too brief. It omits essential context about sentry types, condition logic, and how the tool integrates into CMMN workflows, leaving significant gaps for the agent.

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 description coverage is 100%, so each parameter is documented in the schema. The description adds minimal extra meaning (only references 'multiple conditions, evaluation modes'), but the schema already defines them adequately.

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 'Creates', the resource 'CMMN Sentry', and specifies 'optional CMMN 1.1 enhancements'. It distinguishes itself from sibling tools like update, evaluate, reset sentries.

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

Usage Guidelines2/5

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

The description provides no guidance on when to use this tool versus alternatives. With many sentry-related siblings (evaluate, update, reset, etc.), the agent lacks direction on appropriate usage contexts or exclusions.

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/mstang/casemgr-mcp'

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