token-saver
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 |
|---|---|
| check_outputA | Analyze a text output from a Claude API response. Returns an alert level (info/warning/error/alert), token count, whether the output should be suppressed, and detected waste patterns. Use after every API response to catch token-heavy or ignored output early. |
| get_session_statsA | Return cumulative session statistics: total tokens analyzed, tokens suppressed, and counts of warnings/errors/alerts fired. Use to understand overall waste in the current session. |
| reset_session_statsA | Reset all session statistics to zero. |
| analyze_historyA | Analyze a conversation messages array for repetitive or ignored content. Identifies near-duplicate messages and large log-pattern outputs the user likely skipped. Returns suggested truncation count and estimated token savings. |
| set_modeA | Switch the plugin mode. "off" (default) — plugin is silent, all analysis is skipped. "monitor" — analyze and report but never suppress. "active" — full analysis with suppression. Returns the applied mode. |
| set_thresholdsB | Override alert thresholds for the current session. All values are in estimated tokens. Returns the applied configuration. |
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 6 tools
Each tool targets a distinct aspect of token analysis and suppression: conversation history analysis, single output check, session statistics, reset, mode switching, and threshold configuration. No overlap in purpose.
All tool names follow a consistent verb_noun pattern in snake_case (e.g., analyze_history, check_output, set_mode), making them predictable and easy to understand.
With 6 tools, the server is well-scoped for its domain. Each tool serves a necessary function without redundancy or missing core operations.
The tool set covers all essential operations: analysis, monitoring, statistics, configuration, and reset. There are no obvious gaps for the stated purpose of token waste detection and suppression.