Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
NO_COLORNoSet to print tool calls without grey text.
MEMORY_DBNoWhere memories are stored../memory.db
AGENT_MODELNoAny Ollama model with tool support, e.g. qwen3:8b, llama3.1:8b.qwen3:4b
EMBED_MODELNoEmbedding model used for semantic recall. If you change it, delete memory.db because vectors from different models can't be compared.nomic-embed-text
OLLAMA_HOSTNoOllama server URL.http://localhost:11434

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
}

Tools

Functions exposed to the LLM to take actions

NameDescription
rememberA

Save one durable fact to long-term memory.

Write it as a short standalone sentence that makes sense out of context, e.g. "The user's name is Priya and she works in Bengaluru." Use for preferences, personal facts, decisions and project details. Do not save small talk, secrets or passwords.

recallA

Search long-term memory for facts relevant to the query.

Call this before answering anything that might depend on what you already know about the user or their projects.

forgetA

Delete one memory by its id (ids come from recall or list_memories).

list_memoriesB

List the most recent memories, newest first.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A3.7/5.0

Scored across 4 tools

Disambiguation5/5

Each tool maps to a distinct memory operation: remember writes, recall searches semantically, list_memories enumerates recent items, and forget deletes by id. The descriptions reinforce the boundaries, so an agent can pick the right one without hesitation.

Naming Consistency4/5

All names are snake_case and verb-led, which is easy to parse. The only deviation is list_memories (verb_noun) versus the single-verb remember/recall/forget, a minor inconsistency rather than a real problem.

Tool Count5/5

Four tools is exactly right for a scoped long-term memory store, covering write, search, browse and delete without padding. Nothing feels redundant or missing at this size.

Completeness4/5

The full lifecycle is nearly covered: create, retrieve via search or listing, and delete. There is no dedicated update/edit tool, so correcting a fact requires forget-then-remember, a small gap agents can work around.

Maintenance

ActivityMaintained
ResponsivenessNo recent community issues