DeadBolt
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| deadbolt_get_integration_guideA | Get local, read-only DeadBolt setup steps for a supported integration route. Returns operator responsibilities, a placeholder configuration and the enforcement boundary. Does not create files, run a server or grant permission. Available only when operator configuration is blank. |
| deadbolt_check_bundleA | Read the bundled engine and provenance metadata, calculate its SHA-256 and report compatibility and packaging integrity for this host. Reads only this installed bundle; does not execute the engine, inspect operator state or test security. Available only when operator configuration is blank. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 2 tools
The two tools have clearly distinct purposes: one returns human-readable setup guidance, the other computes bundle integrity/hash metadata. Their descriptions explicitly state what each does and does not do, leaving no realistic room for misselection.
Both names use the same server prefix plus a consistent verb_noun pattern (deadbolt_get_integration_guide, deadbolt_check_bundle), with no mixed casing or style drift.
Two tools is thin even for a narrow, read-only pre-configuration surface; an agent will likely need more than guidance plus a bundle check. The count is not wrong, but it is borderline minimal.
The surface covers the two advertised functions (setup guidance, bundle verification) but has notable gaps: no way to enumerate supported integration routes, validate a candidate placeholder config, or confirm host prerequisites beyond the bundle hash. Agents hitting those needs have no tool path.