tarelab
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 |
|---|---|
| tare_wrappedB | Where this machine's coding-agent tokens and money went (Claude Code, Codex CLI, Gemini CLI, Cline, Roo Code, Kilo Code): API-equivalent spend, plan-limit use, what filled the context, cache rebuilds, highlights and the top fixes with estimated savings. Local and free. |
| tare_receiptB | Cost per commit before and after Tare's fixes were installed, with a 90% range, or a plain 'not enough data yet'. |
| tare_cacheA | For one session transcript: context size, whether the prompt cache is still warm, and what the next message will cost warm versus cold. |
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 targets a distinct analysis layer: aggregate spend summary (tare_wrapped), per-commit cost comparison (tare_receipt), and per-session cache diagnostics (tare_cache). There is some thematic overlap since all report cost/context metrics, but the descriptions make the boundaries clear enough to select correctly.
All three tools follow the exact same pattern: 'tare_' prefix plus a single lowercase noun (wrapped, receipt, cache), all in snake_case. No deviation whatsoever.
Three tools is on the low end but appropriate for a focused cost-analytics server; each covers a genuinely different view (overall, per-commit, per-session). It earns its place, though one could imagine a fourth for session listing or trend history.
The surface covers the core analytics: spend overview, before/after fix comparison, and cache cost projection. Minor gaps exist—no way to list sessions or agents, filter by time range, or drill into individual fixes—but agents can work around these for the stated purpose.