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
{
  "listChanged": true
}

Tools

Functions exposed to the LLM to take actions

NameDescription
zipmem_load_memoryA

Load this project's compressed long-term memory. CALL THIS FIRST, at the very start of every session, before doing anything else. Returns architectural blueprints, file-coordinate anchors, and lessons learned from previous sessions so you regain full context at near-zero token cost.

zipmem_save_and_compactA

Compress the current session and merge it into long-term memory. CALL THIS when the user signals they are done (exit/quit/goodbye/wrap up) OR when you sense your context window is nearing capacity. Provide your work as structured sections: blueprints (verbatim architecture/schemas/decisions), anchors (file coordinates instead of raw code), and lessons (distilled bug fixes). Never include raw code blocks — use anchors.

zipmem_checkpointA

Stage incremental progress for crash-safety. Call this PERIODICALLY during a session — after each meaningful unit of work (a feature wired up, a bug fixed, a decision made) — so that an abrupt exit (Ctrl+C, a closed terminal, a crash) never loses more than the last few steps. It is cheap and does NOT finalize the session: pass the same structured fields as save_and_compact (blueprints/anchors/lessons + a running summary). The data is buffered durably and folded into memory automatically on the next session if the current one ends without a clean compaction.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A4.2/5.0

Scored across 3 tools

Disambiguation5/5

Each tool has a distinct purpose: zipmem_load_memory initializes context, zipmem_checkpoint stages incremental progress, and zipmem_save_and_compact finalizes and compresses. No overlap or ambiguity.

Naming Consistency4/5

All tools share the 'zipmem_' prefix and use lowercase with underscores, but 'zipmem_checkpoint' deviates slightly from the verb_noun pattern used by the other two (load_memory, save_and_compact). Still, the naming is clear and predictable.

Tool Count5/5

With only three tools, the set is minimal but perfectly scoped for the server's purpose: loading, checkpointing, and saving memory. Each tool is essential and justified.

Completeness5/5

The tools cover the complete lifecycle of memory management: initial load, periodic checkpoints, and final save/compact. No gaps are present for the intended domain.

Maintenance

ActivityInactive
ResponsivenessNo issues