behavior-mcp

Overview Schema Source Related Servers Discussions Admin

register_trigger

Configure or list reactive interrupt triggers with priority preemption and cooldown guards for behavior trees, enabling automatic condition-based interrupts instead of manual pauses.

Instructions

Configure or list reactive interrupt triggers with priority preemption and cooldown guards (actions: register, list). Use register_trigger instead of abort_behavior when defining automatic condition-based interrupts rather than manually pausing or stopping a tree.

Returns registered trigger configuration, ID, or trigger list.

Input Schema

TableJSON Schema

Name	Required	Description
`name`	No	Trigger name
`action`	Yes	Trigger operation: register, list
`project`	No	Target project slug
`priority`	No	Preemption priority
`trigger_id`	No	Trigger ID
`cooldown_ms`	No	Minimum cooldown interval between fires
`behavior_name`	No	Behavior tree to activate when condition fires
`condition_type`	No	Condition type (e.g. hp_threshold, enemy_proximity)
`condition_params`	No	Condition evaluation parameters

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedv0.3.1Oct 1, 2026
- changedInput schema / properties / action / description
```
Previous value: -"Trigger operation"New value: +"Trigger operation: register, list"
```
- addedInput schema / properties / action / enum
```
Added value: +[
+  "register",
+  "list"
+]
```
Changed14 schema fields changedv0.2.1Sep 24, 2026
- removedInput schema / $schema
```
Removed value: -"http://json-schema.org/draft-07/schema#"
```
- removedInput schema / additionalProperties
```
Removed value: -false
```
- addedInput schema / properties / action / description
```
Added value: +"Trigger operation"
```
- removedInput schema / properties / action / enum
```
Removed value: -[
-  "register",
-  "list"
-]
```
- addedInput schema / properties / behavior_name / description
```
Added value: +"Behavior tree to activate when condition fires"
```
- removedInput schema / properties / condition_params / additionalProperties
```
Removed value: -true
```
- addedInput schema / properties / condition_params / description
```
Added value: +"Condition evaluation parameters"
```
- removedInput schema / properties / condition_params / properties
```
Removed value: -{}
```
- addedInput schema / properties / condition_type / description
```
Added value: +"Condition type (e.g. hp_threshold, enemy_proximity)"
```
- addedInput schema / properties / cooldown_ms / description
```
Added value: +"Minimum cooldown interval between fires"
```
- addedInput schema / properties / name / description
```
Added value: +"Trigger name"
```
- addedInput schema / properties / priority / description
```
Added value: +"Preemption priority"
```
- addedInput schema / properties / project / description
```
Added value: +"Target project slug"
```
- addedInput schema / properties / trigger_id / description
```
Added value: +"Trigger ID"
```
First observedv0.1.2Sep 10, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations declare the write/non-idempotent/non-destructive profile, so the description's extra value is the domain behavior it adds: preemption-by-priority and cooldown guarding between fires. It does not describe persistence, permission requirements, or what a failed registration does, which keeps it short of a 5.

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?

Two sentences, front-loaded with purpose and the sibling-routing rule before the trailing return-value note. The final sentence is partly redundant with the follow-on description text but is short enough to justify itself.

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?

Covers the two actions, the key configuration concepts, the return shape (configuration, ID, or list), and the sibling routing for a 9-parameter tool with no output schema. Nested condition_params is left to the schema, which is acceptable.

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 every parameter already carries its own description (priority, cooldown_ms, condition_type, etc.). The description repeats the register/list action split but adds no format or constraint detail beyond the schema, so the baseline 3 applies.

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 and resource ('Configure or list reactive interrupt triggers') and names the distinctive behavioral features (priority preemption, cooldown guards). It clearly differentiates itself from the sibling abort_behavior, so an agent can pick between them without opening a schema.

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?

Explicitly states when to prefer this tool over abort_behavior: 'defining automatic condition-based interrupts rather than manually pausing or stopping a tree.' That is a named alternative plus the condition that selects it.

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

Deploy Server

register_trigger

Instructions

Input Schema

Schema Changelog

TDQS

Other Tools