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
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
memory_project_scopeA

Resolve the project bank (user_id / dataset) and access policy for a workspace path. Call it instead of guessing a bank name. Local mapping only.

memory_addA

Store durable facts, decisions or session notes in the active provider. Pass bank from memory_project_scope for project work. Hindsight ingests async by default.

memory_searchA

Return ranked raw hits from stored memories. memory_recall suits questions; memory_reflect synthesizes an answer.

memory_recallB

Retrieve stored context for a natural-language question (Hindsight recall; search on mem0 and Cognee).

memory_forgetA

Delete memories: mem0 needs memory_id; on Hindsight a bank without memory_id drops the whole bank. Confirm with the user first. Not available on Cognee.

memory_exportA

Export memories as PMM v1 JSON or JSONL for backup or migration. Pass bank for large stores.

memory_importA

Import a PMM v1 payload from memory_export. Content and scope carry over; embeddings and graphs do not.

memory_provider_statusB

Report the active provider id and backend URL.

memory_reflectA

Synthesize a reasoned answer from stored memories, with evidence. The answer is not stored.

memory_consolidateA

Rebuild the provider's graph or index after bulk ingest (Cognee cognify; no-op on mem0).

memory_pages_listA

List a bank's knowledge pages (ids, names, folders; no bodies). Hindsight only.

memory_pages_searchA

Search knowledge pages: past decisions and conventions. Check them before fixing a bug, changing a test or building something; verify claims against the code. Hindsight only.

memory_pages_readA

Read one knowledge page by id (from a page listing, search, or [[page:]] link). Hindsight only.

memory_capture_initiativeA

Record an approved feature plan as a knowledge page before writing code; relates_to_page_id records a plan change. Skip bug fixes and small tweaks. Hindsight only.

memory_statusA

Report whether async ingest has drained (ready, active and failed counts, memory_add operation ids). Check before recalling just-stored content. Hindsight only; mem0 is always ready.

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 15 tools

Disambiguation4/5

The three retrieval tools (search/recall/reflect) overlap conceptually, but each description explicitly says when to use which (raw hits vs. context vs. synthesized answer), which resolves most of the confusion. memory_status vs. memory_provider_status are also close (ingest drain vs. provider id/URL) but are distinguishable by their stated outputs; memory_add vs. memory_import is clear from the PMM payload requirement.

Naming Consistency4/5

Every name uses the memory_ prefix in snake_case, giving a strong shared convention. The only deviation is word order: memory_pages_list/search/read put the verb last while memory_add, memory_search and memory_forget put it directly after the prefix, so the pattern is predictable but not perfectly uniform.

Tool Count4/5

15 tools sits at the top of the sensible band and is justified by the breadth of the surface: three provider backends, ingest lifecycle, pages and export/import. Nothing looks like filler, though the provider-specific optionality (Hindsight-only, mem0-only, Cognee-only tools) means several tools are dead for any given user.

Completeness3/5

Storage, retrieval, sync, backup and page reading are covered, but there are clear gaps: no memory_update/overwrite tool, and knowledge pages can be listed, searched and read but not edited or deleted except by dropping a whole bank via memory_forget. Page creation exists only through memory_capture_initiative for feature plans, so an agent cannot add or revise a convention page directly.

Maintenance

ActivityMaintained
ResponsivenessOutdated data