behavior-mcp

Overview Schema Source Related Servers Discussions Admin

load_behavior

Destructive

Load, unload, or hot-swap a behavior tree instance in the browser runtime. Use for executing active behavior trees at runtime, not for registering or inspecting definitions.

Instructions

Load, unload, or hot-swap a behavior tree instance in the browser runtime (actions: load, unload, swap). Use load_behavior instead of manage_behaviors when executing an active behavior tree instance at runtime rather than registering or inspecting definitions.

Returns execution handle, runtime state, active node, and session/intention bindings.

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": {
      "action": "<action>",
      "behavior_name": "<behavior_name>"
    },
    "name": "load_behavior"
  }
}

Input Schema

Name	Required	Description
`action`	Yes	Behavior loading operation: load, unload, swap
`project`	No	Target project slug
`trace_id`	No	Distributed trace ID for cross-server correlation
`intention`	No	Optional linked intention payload matching the dispatch token
`parameters`	No	Initial execution parameters
`session_id`	No	Linked state-memory session ID
`intention_id`	No	Linked agent-reasoning intention ID
`behavior_name`	Yes	Name of the behavior tree to load
`dispatch_token`	No	Cryptographically signed dispatch token issued by agent-reasoning-mcp (gate_intention)
`behavior_version`	No	Version of behavior tree (defaults to latest)
`client_request_id`	No	Idempotency key

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedv0.4.1Oct 4, 2026

addedInput schema / properties / dispatch_token

Added value: +{
+  "description": "Cryptographically signed dispatch token issued by agent-reasoning-mcp (gate_intention)",
+  "properties": {
+    "aud": {
+      "type": "string"
+    },
+    "behavior_name": {
+      "type": "string"
+    },
+    "expires_at": {
+      "type": "string"
+    },
+    "hmac_signature": {
+      "type": "string"
+    },
+    "intention_id": {
+      "type": "string"
+    },
+    "issued_at": {
+      "type": "string"
+    },
+    "params_hash": {
+      "type": "string"
+    },
+    "token_id": {
+      "type": "string"
+    }
+  },
+  "type": "object"
+}

addedInput schema / properties / intention

Added value: +{
+  "description": "Optional linked intention payload matching the dispatch token",
+  "type": "object"
+}

Changed2 schema fields changedv0.3.1Oct 1, 2026

changedInput schema / properties / action / description

Previous value: -"Behavior loading operation"New value: +"Behavior loading operation: load, unload, swap"

addedInput schema / properties / action / enum

Added value: +[
+  "load",
+  "unload",
+  "swap"
+]

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: +"Behavior loading operation"
```
- removedInput schema / properties / action / enum
```
Removed value: -[
-  "load",
-  "unload",
-  "swap"
-]
```
- addedInput schema / properties / behavior_name / description
```
Added value: +"Name of the behavior tree to load"
```
- addedInput schema / properties / behavior_version / description
```
Added value: +"Version of behavior tree (defaults to latest)"
```
- addedInput schema / properties / client_request_id / description
```
Added value: +"Idempotency key"
```
- addedInput schema / properties / intention_id / description
```
Added value: +"Linked agent-reasoning intention ID"
```
- removedInput schema / properties / parameters / additionalProperties
```
Removed value: -true
```
- addedInput schema / properties / parameters / description
```
Added value: +"Initial execution parameters"
```
- removedInput schema / properties / parameters / properties
```
Removed value: -{}
```
- addedInput schema / properties / project / description
```
Added value: +"Target project slug"
```
- addedInput schema / properties / session_id / description
```
Added value: +"Linked state-memory session ID"
```
- addedInput schema / properties / trace_id / description
```
Added value: +"Distributed trace ID for cross-server correlation"
```
First observedv0.1.2Sep 10, 2026

TDQS

A4.1/5.0

Behavior3/5

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

Annotations already declare destructiveHint=true, idempotentHint=false, and openWorldHint=false, so the safety profile is covered structurally. The description adds return-shape context (execution handle, runtime state, active node, bindings) and the hot-swap concept, but says nothing about permission requirements, the effect of unload on existing state, or the fact that non-idempotent calls may duplicate without client_request_id. Useful, but not rich for a destructive 11-param mutation.

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?

Three compact sentences, front-loaded with purpose and routing before return details. The parenthetical '(actions: load, unload, swap)' mildly repeats the opening verb list, a small redundancy, but nothing else is wasted.

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?

For a complex, nested-parameter, destructive tool with no output schema, the description adequately covers what it does, when to prefer it, and roughly what comes back. It stops short of covering the dispatch_token authorization gate and the destructive consequences of unload, which are the main remaining gaps.

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 all 11 parameters including dispatch_token, behavior_version, and client_request_id are documented in the schema itself. The description adds no syntax, format, or dependency guidance beyond the action enum already visible in the schema, so the baseline of 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?

The description names three specific verbs (load, unload, swap) applied to a concrete resource (behavior tree instance in the browser runtime) and enumerates the action values. It explicitly distinguishes itself from the sibling manage_behaviors, so an agent can select it without opening either 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?

It states the selecting condition directly: use this instead of manage_behaviors when executing an active tree at runtime rather than registering or inspecting definitions. That is an explicit when-to-use plus named alternative, exactly what routing needs.

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

Deploy Server