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
rememberA

Propose a new memory. It is recorded as PENDING and does not govern until a human approves it (agents propose, humans approve). Set CONXT_AUTO_APPROVE=1 for frictionless solo use.

recallA

Recall approved memories relevant to a query. Only human-approved memories are returned — pending or rejected ones never surface.

list_pendingA

List memories awaiting human approval, so they can be reviewed and approved or rejected.

approveA

Approve a pending memory (a human action). Once approved it governs and, if cloud sync is configured, is pushed to Conxt.

rejectB

Reject a pending memory so it never governs.

forgetC

Delete a memory by id.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A3.6/5.0

Scored across 6 tools

Disambiguation5/5

Each tool has a clearly distinct role in the memory lifecycle: remember proposes, recall retrieves approved, list_pending shows pending, approve/reject take opposite actions on pending, and forget deletes. No two tools appear to do the same thing, and the descriptions reinforce their unique purposes.

Naming Consistency4/5

All tool names are lowercase verbs, but list_pending uses an underscore while the others are single words (remember, recall, approve, reject, forget). This is a minor deviation but the pattern is still predictable—most are simple imperatives. The inconsistency is small enough to not cause confusion.

Tool Count5/5

With 6 tools, the server is well-scoped for a memory management system. It covers the essential operations without redundancy, and the count feels appropriate—not overly thin nor bloated.

Completeness3/5

The server covers create (remember), read (recall), and delete (forget) for approved memories, plus approval workflow tools (list_pending, approve, reject). However, there is no update/modify operation for existing memories, and no way to list all approved memories (recall only returns relevant ones). These gaps, particularly the missing update capability, mean the lifecycle is not fully complete.

Maintenance

ActivityMaintained
ResponsivenessNo issues