Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
CCRYSTAL_STORENoPath to the decoupled context store. When set, crystals, entity logs, and transient leases are written to an isolated companion repository instead of the default in-tree .ccrystals/ directory.

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
{}
prompts
{}
resources
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
crystal_batchB

Execute compound semicolon-delimited atomic transition recipes (e.g. 'node add -s "..." demo; task done -t task-1 demo'). Maximizes efficiency by minimizing roundtrips.

crystal_searchB

Search and list crystals in the cave with multi-dimensional filtering (query text, temporal bounds, leases, tasks, lessons, status, aging, archived, sorting, and pagination). When called without filters, lists active crystals (most recently active first).

crystal_statsB

Compute and inspect workspace cave statistics, temporal genesis, structural totals, physical disk footprints, and quantitative prompt token savings across global cave or filtered search criteria.

crystal_initC

Initialize a new context crystal.

crystal_checkpointC

Create an anchor checkpoint node in the crystal DAG.

crystal_task_transitionC

Add or complete a task in a crystal.

crystal_goal_transitionB

Transition a crystal's top-level goal status (conclude successfully, abandon, or reopen) with optional resolution summary or reason.

crystal_transient_leaseC

Create, clean, or promote a transient resource lease.

crystal_slice_forkC

Extract crystal fragment or fork sub-DAG into a new crystal.

crystal_pruneB

Permanently prune a crystal or cold storage archives by retention policy (with entity and artifact cascade).

crystal_artifactC

Register, list, or inspect virtual and physical artifacts across cave or crystal.

crystal_hydrateC

Hydrate context beam from a crystal with selective shaping (tail, slice range from/to, depth, or summary only).

crystal_triageB

Triage workspace cave crystals for lifecycle hygiene and aging, categorizing them into keep (active), candidates for cleanup (concluded/abandoned with 0 open leases), and requires review.

crystal_archiveA

Archive a concluded or inactive crystal to cold storage (.ccrystals/archive/) to reduce cave bloat while preserving all state and artifacts.

crystal_unarchiveA

Restore an archived crystal from cold storage (.ccrystals/archive/) back to the active cave.

crystal_meltC

Melt and squash intermediate sub-DAG transitions into a single consolidated checkpoint node with aggregated artifact links (Zero-LLM deterministic squashing by default).

crystal_connectB

Connect, disconnect, or inspect directed lattice bonds between crystals in the cave, enforcing an acyclic graph invariant and supporting cross-crystal context hydration.

Prompts

Interactive templates invoked by user choice

NameDescription
hydrate_contextHydrate context beam system prompt from crystal
triage_caveInspect and triage crystals across the workspace cave for lifecycle hygiene and cleanup recommendations

Resources

Contextual data attached and managed by the client

NameDescription
State for release-v1-3-0-extensions-media-and-mcp-optimizationLiving state container JSON
DAG for release-v1-3-0-extensions-media-and-mcp-optimizationLineage and DAG nodes JSON
Hydrated context beam for release-v1-3-0-extensions-media-and-mcp-optimizationHydrated context beam text/markdown
Artifacts for release-v1-3-0-extensions-media-and-mcp-optimizationArtifacts and physical substrates JSON
Lattice bonds for release-v1-3-0-extensions-media-and-mcp-optimizationLattice bonds and inbound/outbound topology JSON
Cave Entities RegistryRegistered cave entities and identities
Cave Artifacts RegistryRegistered cave artifacts and world-state substrates

TDQS

B3.3/5.0

Scored across 17 tools

Disambiguation4/5

Most tools target distinct lifecycle operations (init, checkpoint, task/goal transition, hydrate, archive/unarchive, prune, connect). A few overlap conceptually—checkpoint vs melt both manipulate DAG nodes, and several tools bundle multiple actions (crystal_artifact handles register/list/inspect; crystal_transient_lease handles create/clean/promote)—but descriptions keep boundaries clear enough.

Naming Consistency5/5

Every tool follows the crystal_<snake_case_noun/verb> pattern consistently, with readable and predictable suffixes. No camelCase or stylistic drift.

Tool Count4/5

17 tools is on the heavier side but justified by a rich domain (DAG lifecycle, leasing, artifacts, archival, bonding). Each tool maps to a distinct operation, though a couple could theoretically be merged.

Completeness4/5

Covers the full lifecycle: init, checkpoint, task/goal transitions, leases, forking, hydration, triage, archive/unarchive, melt, prune, connect, search, stats, and batch. Some minor gaps (e.g. no rename/update-metadata or explicit delete beyond prune) but core workflows are complete.

Maintenance

ActivityActive
ResponsivenessNo issues