behaviorlock
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| prompts | {
"listChanged": true
} |
| resources | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| behaviorlock_validateA | Validate a behavior contract and optional portable trace files without comparing them. |
| behaviorlock_compareB | Compare a baseline and candidate trace against deterministic observable-behavior contracts. |
| behaviorlock_explainC | Compare traces and return one assertion with selected baseline/candidate values and the exact reason. |
| behaviorlock_fingerprintA | Create a stable SHA-256 fingerprint of scenario status and observations, excluding run metadata. |
| behaviorlock_renderC | Compare traces and render JSON, Markdown, standalone HTML, SARIF, or JUnit XML. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| gate-agent-upgrade | Design a deterministic observable-behavior contract before changing an agent |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| contract-schema | Behaviorlock contract JSON Schema |
| trace-schema | Portable behavior trace JSON Schema |
| example | Complete behavior compatibility contract |
TDQS
Scored across 5 tools
The five tools have distinct roles: render formats output, validate checks contracts without comparison, compare runs comparisons, explain provides detailed assertion reasoning, and fingerprint generates hashes. While render and explain both involve comparison, their output purposes are clearly differentiated.
All tool names follow a consistent pattern: lowercase snake_case with the server prefix 'behaviorlock_' followed by a single verb. This is uniform and predictable.
Five tools is an appropriate, focused set for a behavior contract comparison utility—not too few, not excessive.
The tool set covers validation, comparison, explanation, rendering, and fingerprinting, providing a complete workflow for observing and debugging behavior-contract compliance.