TokenTrust
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": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| verify_proxy_savingsA | Runs an independent, adversarial verification of an AI-coding-agent context-reduction proxy's (rtk, headroom) claimed token and cost savings, using the same TT01-TT05 engine as Side effects: read-only against Parameters: Returns: the same structured JSON |
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 1 tool
Only one tool exists, so there is no possibility of confusing it with another tool. The tool's purpose is clearly described, and its parameters are well-defined.
The single tool name follows a clear verb_noun pattern (verify_proxy_savings), and with only one tool there is no inconsistency to evaluate.
The server exposes only one tool, which feels too thin for a platform named TokenTrust that implies a broader verification suite. While the tool is complex, a single tool limits the server's ability to support related operations.
The tool covers the core verification workflow (standard, cross-tool comparison, live mode, regression diff), but lacks supporting operations such as listing supported proxies, retrieving historical runs, or accessing task corpus details. These are notable gaps that an agent might need.