Skip to main content
Glama
omkar9854

slimctx-token-optimizer

by omkar9854

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
slimctx_compressA

Compress large tool output, logs, JSON, or file content before reasoning over it. Returns a compact version that preserves errors, outliers, and query-relevant content. If the result contains a [slimctx-ref ...] marker, the full original can be recovered with slimctx_retrieve.

slimctx_retrieveA

Recover the byte-exact original content for a [slimctx-ref ] marker seen in previously compressed output.

slimctx_statsC

Token savings accumulated in this session.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A3.6/5.0

Scored across 3 tools

Disambiguation5/5

Each tool has a clearly distinct role: compress creates a reference, retrieve recovers original content from a reference, and stats reports session token savings. No overlap or ambiguity between them.

Naming Consistency5/5

All tool names follow a consistent 'slimctx_' prefix followed by a clear verb: compress, retrieve, stats. The pattern is uniform and predictive.

Tool Count5/5

Three tools is an ideal size for this focused server. Each tool is essential to the compression-retrieval-stats lifecycle, and no redundant or extraneous tools exist.

Completeness5/5

The tool surface fully covers the domain: compressing content, retrieving it when needed, and tracking token savings. There are no obvious workflow gaps for the stated purpose.

Maintenance

ActivitySlowing
ResponsivenessNo issues