Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault

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

CapabilityDetails
tools
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
tokendiet_prune_tool_outputB

Prune noisy CLI, pytest, tsc, or build logs to a token budget using the C++20 Order-Preserving Salience Knapsack while keeping error/traceback anchors.

tokendiet_skeletonize_codeA

AST-skeletonize Python files by keeping imports, signatures, docstrings, and focus symbols while eliding long unfocused helper bodies.

tokendiet_compress_sessionC

Compress a multi-turn coding-agent trace using C++20 cross-turn read deduplication, log pruning, and AST skeletonization.

tokendiet_route_finopsC

Route an agent turn across Local Flash, Balanced Coding, and Frontier Reasoning tiers with Cascade Escalation Guard.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

B3.1/5.0

Scored across 4 tools

Disambiguation4/5

Each tool targets a distinct operation: log pruning, code skeletonization, session compression, and cost-tier routing. However, compress_session explicitly bundles log pruning and AST skeletonization, so its boundary with prune_tool_output and skeletonize_code is fuzzy—an agent may pick the narrower tool when the session-level one was intended (or vice versa).

Naming Consistency5/5

All four tools share the tokendiet_ prefix and follow a consistent snake_case verb_noun pattern (prune_tool_output, skeletonize_code, compress_session, route_finops). The naming is predictable and readable.

Tool Count4/5

Four tools is a lean, well-scoped surface where each tool maps to a distinct compression/routing concern, with no filler. It is slightly thin—nothing handles token counting or budget configuration—but nothing is redundant.

Completeness4/5

The set covers the main workflow: prune logs, skeletonize code, compress a full trace, and route to model tiers. It lacks a standalone token-count/budget-estimation utility and any way to inspect or tune pruning/skeletonization settings, which agents would likely want before committing to a compression budget.

Maintenance

ActivityMaintained
ResponsivenessNo recent community issues