behavior-mcp

Overview Schema Source Related Servers Discussions Admin

get_status

Read-onlyIdempotent

Query active behavior tree execution status, history, or full node traversal state to inspect current paths, tick counters, duration, and errors.

Instructions

Query active behavior execution status, history, or full tree node traversal state (actions: current, history, tree_state). Use get_status instead of get_metrics when inspecting active execution state and node traversal paths rather than aggregated runtime performance telemetry.

Returns execution status, current node path, tick counters, duration, and error states.

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>"
    },
    "name": "get_status"
  }
}

Input Schema

Name	Required	Description
`limit`	No	Max history entries
`action`	Yes	Status query mode: current, history, tree_state
`project`	No	Target project slug
`execution_id`	No	Target execution ID (or latest if omitted)

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedv0.3.1Oct 1, 2026

changedInput schema / properties / action / description

Previous value: -"Status query mode"New value: +"Status query mode: current, history, tree_state"

addedInput schema / properties / action / enum

Added value: +[
+  "current",
+  "history",
+  "tree_state"
+]

Changed7 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: +"Status query mode"
```
- removedInput schema / properties / action / enum
```
Removed value: -[
-  "current",
-  "history",
-  "tree_state"
-]
```
- addedInput schema / properties / execution_id / description
```
Added value: +"Target execution ID (or latest if omitted)"
```
- addedInput schema / properties / limit / description
```
Added value: +"Max history entries"
```
- addedInput schema / properties / project / description
```
Added value: +"Target project slug"
```
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 already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so the safety profile is covered. The description adds value beyond that by enumerating what is returned (execution status, node path, tick counters, duration, error states), which matters since there is no output schema. It stops short of noting auth requirements, rate limits, or pagination behavior for history.

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 tight sentences with the action modes and the routing rule front-loaded, followed by the return summary. Very little waste, though the parenthetical enum listing is mildly redundant with the schema.

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 read-only query tool with full schema coverage and safety annotations, the definition covers purpose, alternatives, and return fields, compensating for the absent output schema. Minor gaps remain around history pagination and default-to-latest execution behavior.

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 the schema already documents action, project, execution_id, and limit. The description's parenthetical restates the action enum but adds no new syntax or format detail. Baseline 3 is appropriate when the schema carries the parameter burden.

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 (Query) and resource (behavior execution status/history/tree traversal), and enumerates the three action modes. It also names the sibling get_metrics and explains the distinction, so an agent can differentiate without opening any 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 says to use get_status instead of get_metrics and gives the selecting condition: inspecting active execution state and node traversal paths vs. aggregated runtime performance telemetry. This is a full when/when-not/alternative statement.

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

Deploy Server