Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
MEMEX_API_TOKENNoAPI token for Bearer auth (opt-in, off by default)
MEMEX_AUDIT_LOGNoSet to 'true' to enable audit logging (opt-in)
MEMEX_AUTO_BACKUPNoSet to 'true' to enable auto-backup (opt-in)
MEMEX_AUTO_UPDATENoSet to 'true' to enable auto-update (opt-in)
MEMEX_AUTO_CLEANUPNoSet to 'true' to enable auto-cleanup (opt-in)
MEMEX_ENCRYPTION_KEYNoEncryption key for encrypting memory text at rest (opt-in)

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
memex_recallA

Search stored memories for query. Call before answering questions about prior work, decisions, or past conversations. Default mode="fast" (vector search, ~0.1s); use mode="thorough" only when a fast result looks wrong or stakes are high (~3s, hybrid search). Current facts list first, superseded/expired after, marked. Every hit shows its id, status, and recorded date. Fix a stale hit with memex_correct; see its history with memex_get. Do not use this to store a new fact -- use memex_store instead.

memex_storeA

Remember or store one new, self-contained memory verbatim -- exact text, not a summary. Optional valid_from/valid_to/event_at/source, and supersedes (ids this replaces; unknown or another user's ids are rejected). The reply echoes recorded_at and any declared window so you can confirm without a recall. Do not use this to correct something already in memory -- use memex_correct with the old id instead of storing a near-duplicate.

memex_correctA

Correct a memory that is wrong or outdated, in one call: stores text as a new record superseding id. The old record is kept, marked superseded, and stays visible in memex_get's history -- nothing is deleted. id must come from a prior memex_recall or memex_get result; an unknown id is rejected. If id is already superseded, this reports the current replacement instead of writing, unless force=true. Do not use this for a brand-new, unrelated fact -- use memex_store instead.

memex_getA

Fetch exactly one memory by id, verbatim, with its correction chain in both directions: what it replaced (oldest last) and what replaced it (newest last). Use this to resolve a "SUPERSEDED by " marker from memex_recall, or to confirm an id before passing it to memex_correct. An unknown id is an error. Do not use this to find a memory by topic -- use memex_recall instead.

memex_recentA

List memories by recency, no search query needed -- good for "what changed recently" or catching up after time away. since (ISO-8601) is a lower bound: only records at or after it. kind="corrections" shows only memories that corrected an older one, with the id(s) they replaced. Do not use this to find a memory about a topic -- use memex_recall instead.

memex_healthA

Check whether the memory backend is up, and see store-wide stats (current/superseded/expired counts, oldest/newest record, queue and dead-letter depth) in one call. Call this after any other memex_* tool returns isError, before retrying. Do not call this to search memory -- use memex_recall for that.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A4.7/5.0

Scored across 6 tools

Disambiguation5/5

Each tool has a clearly distinct role: recall searches, store adds, correct supersedes, get fetches by id, recent lists by time, and health checks backend status. There is no overlap, and the descriptions actively redirect misuse to the correct tool.

Naming Consistency5/5

All tools share the memex_ prefix followed by a single lowercase word, forming a predictable memex_<operation> pattern. While recent and health are not verbs, the naming is uniform and immediately readable.

Tool Count5/5

Six tools is a well-scoped size for a memory system: search, store, correct, retrieve, list, and health cover the core operations without redundancy. Each tool earns its place and the count feels neither thin nor heavy.

Completeness5/5

The surface covers the full memory lifecycle: storing, searching, retrieving by id, correcting with supersession, recency listing, and backend health. Deletion is intentionally omitted with supersession used instead, so there are no dead ends in the intended workflow.

Maintenance

ActivityActive
ResponsivenessNo issues