Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
DEBUGNoEnable debug logging (true/false)false
LH42_URLNoLakehouse42 API URL (enables LH42 backend)
LH42_API_KEYNoAPI key for authentication

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
rememberA

Store a memory for later recall. Use this to remember important facts, user preferences, decisions, or any information that should persist across conversations.

recallA

Search memories by semantic similarity. Returns the most relevant memories matching the query.

forgetA

Delete a specific memory by ID. Use when information is outdated or incorrect.

list_memoriesB

List recent memories. Useful for reviewing what has been remembered.

memory_statusA

Get status of the memory system including backend type and features available.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A3.9/5.0

Scored across 5 tools

Disambiguation5/5

Each tool targets a distinct action: remember stores, recall searches, forget deletes, list_memories lists, and memory_status reports system status. There is no ambiguity or overlap between them.

Naming Consistency4/5

Names are mostly verb-based and readable, but there is a slight inconsistency: remember, recall, and forget are bare verbs, while list_memories is verb_noun and memory_status is noun_noun. A more uniform pattern like get_memory_status would improve consistency.

Tool Count5/5

With 5 tools, the server is well-scoped for a memory system. Each tool covers a necessary function without redundancy, making the set neither too thin nor overly heavy.

Completeness4/5

The tools cover the core CRUD operations (create, read, delete) plus status. The only minor gap is the lack of an explicit update tool, but users can forget and re-remember to modify entries, so the shortfall is easily worked around.

Maintenance

ActivityInactive
ResponsivenessNo issues