Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
MEMFIX_MASTER_KEYNoSet to encrypt fact payloads per namespace.
MEMFIX_DATABASE_URLNoSet to postgresql://... for Postgres. SQLite is used by default.

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": false
}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}
experimental
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
memory_assertC

Store a fact with provenance. Returns the fact id.

memory_searchC

Search the current-truth view (tombstoned facts never surface).

memory_correctC

Natural-language correction, e.g. 'forget that I prefer tea'.

memory_retractB

Tombstone a fact. It is never hard-deleted.

memory_auditC

Junk report: duplicates, contradictions, orphans, stale facts.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

B3.1/5.0

Scored across 5 tools

Disambiguation4/5

Each tool targets a distinct action on memory facts: search reads, assert creates, retract tombstones, audit reports quality, correct applies natural-language fixes. The only mild overlap is between memory_correct and memory_retract, since a natural-language correction may imply a retraction, but the descriptions distinguish them (NL correction vs. explicit tombstone).

Naming Consistency5/5

All five tools use a consistent memory_verb snake_case pattern with clear, distinct verbs. No mixing of conventions or verb styles.

Tool Count5/5

Five tools is well-scoped for a memory/fact-management server, covering the essential lifecycle operations without redundancy or bloat. Each tool earns its place.

Completeness4/5

The surface covers create (assert), read (search), update/delete (correct, retract), and quality (audit), which is solid lifecycle coverage. A direct fetch-by-id or explicit fact update tool is missing, though assert returning an id partially mitigates this.

Maintenance

ActivityMaintained
ResponsivenessNo recent community issues