lcc (Local Context Compiler)
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| TYPESAFE_API_KEY | No | API key for the remote TypeSafe API, needed only when using the opt-in `jev` provider (`--provider jev` / `provider: jev`). Not required for the default local providers. | |
| LCC_DISABLE_NETWORK | No | Set to 1 to disable network access (and therefore the optional `jev` provider). | 0 |
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 |
|---|---|
| compactB | Drop context blocks irrelevant to an objective. Default provider mechanical is fully offline (no key, no network); laya is offline semantic (needs the [laya] extra, else honest mechanical fallback); jev needs TYPESAFE_API_KEY. Fail-safe: failures keep content. |
| compact_transcriptA | Tool-call compaction for a session transcript: pairs each tool call with its result, pins the first and newest messages, and drops the pairs a semantic judge says are spent — kept messages stay verbatim, so nothing is summarized. Default 'auto' is the local specialist-v3 ranker (offline, no key); 'jev' is remote and needs TYPESAFE_API_KEY. Every failure keeps the call. |
| inspectA | Read-only diagnostic inspection of a text: tokens, structure, duplication, cleanup projection, and recommendation. Offline. |
| prepareC | Inspect-first deterministic prompt preparation: runs inspection, then lexical selection + safe optimization only when recommended. Never summarizes or paraphrases. Offline. |
| explainB | Explain a relevance-compaction report (as produced by compact): why every block was kept, trimmed, or dropped. Never re-runs, never touches the network. |
| recallA | Return a tool output that compact_transcript (rules_mode 'stashed') replaced with '[removed: N lines, S KB · lcc recall ]'. The bytes are re-hashed on read, so the text is exactly what was removed. Offline, local stash only. |
| intakeB | Intake triage for raw prompt input: readiness with named reasons, non-blocking risk_flags, clarifying questions, a receipt of every filler removed from dictation, and a cache-stable compiled prompt. Offline. |
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 7 tools
Most tools have distinct scopes: intake handles raw prompts, inspect is read-only diagnostics, prepare does deterministic prompt preparation, compact operates on context blocks, and compact_transcript operates on session transcripts. The boundaries are mostly clear, though compact vs compact_transcript and inspect vs prepare could be confused at first glance, requiring the descriptions to disambiguate.
All names are lowercase snake_case and are mostly concise verb-style names. The set is mostly consistent, with minor deviations such as compact_transcript being a compound name while most others are single verbs, and intake reading more like a noun than a verb.
Seven tools is well-scoped for a local context compiler. Each tool appears to earn its place across intake, inspection, preparation, compaction, explanation, and recall, with no obvious filler tools.
The surface covers the main lifecycle: intake, inspect, prepare, compact, compact_transcript, explain, and recall. Minor gaps exist, such as no obvious listing or management operations for stashed outputs or generated reports, but the core workflows are covered and agents can work around these gaps.