TruthGate
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| TRUTHGATE_API_KEY | Yes | Bearer key required for API routes |
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": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| truthgate_preflightC | Compile and gate a task before Hermes uses external tools. |
| truthgate_verifyC | Verify Hermes' final candidate against evidence and tool traces. |
| truthgate_authorizeC | Consume a human-issued approval immediately before a risky action. |
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 3 tools
Each tool has a distinct role: preflight prepares tasks before tool use, verify checks final outputs, and authorize handles human approval. No overlap in purpose.
All tools follow the 'truthgate_verb' pattern with clear action verbs (preflight, verify, authorize), providing a predictable naming scheme.
Three tools is on the smaller side but suitable for a specialized gatekeeping server that handles pre-use, post-use, and approval steps.
The set covers the key stages of the gating workflow: pre-check, verification, and authorization. Minor gaps like handling verification failures are not critical.