tbguard
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| TBGUARD_LEDGER | No | Override the location of the local ledger, which defaults to .tbguard/ledger.jsonl. |
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 |
|---|---|
| guard_contextB | Read files/dirs, drop noise (lockfiles, build output, logs, minified/binary), and pack them under a strict token budget. |
| inspect_fileC | Token count for a file and whether the guard would drop it. |
| savings_summaryB | Total tokens saved across all logged calls. |
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 clear role: guard_context packs files under a budget, inspect_file previews a single file's token count and drop decision, and savings_summary reports aggregate savings. inspect_file overlaps slightly with guard_context since it previews the guard's behavior, but the descriptions make the boundary clear enough.
All names use snake_case and are readable. Two follow a verb_noun pattern (guard_context, inspect_file) while savings_summary is noun_noun, a minor deviation but not confusing.
Three tools is well-scoped for a narrow token-budget/context-packing utility: inspect, pack, and report savings. No tool feels redundant or missing from the count perspective.
The core workflow is covered: inspect a file, pack a context under budget, and view cumulative savings. Minor gaps exist—no way to configure the token budget or drop patterns, and no per-call savings detail or reset—but agents can work around these.