Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
APEX_MEMORY_URLNoThe database URL for the store. Accepts sqlite:///absolute/path/memory.db, sqlite://~/path/memory.db, a bare SQLite file path, or postgresql://user:password@host:port/database. If not set, the default SQLite file ~/.apex-memory/memory.db is used.

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
briefB

Start-of-task read: store identity and open check problems, the index, decisions by status and open status items, then the last log_entries log entries. max_chars caps the index and the status block separately; the log entries always appear in full.

searchA

Search note titles and summaries, sections and log entries. mode: 'bm25' (ranked keywords; hits that hold more of the query terms rank higher, and weak hits holding few of them drop out), 'exact' (whole words or phrase, ignoring case, e.g. ids and hashes) or 'regex' (Python syntax). scope: a domain or folder such as 'project/docs'; empty searches every domain. Hits carry path, section id, heading path, version and a snippet.

readB

Read a whole note (no heading) or one section with its subsections. A section's content has headings relative to it (a direct child is '#'), exactly what patch_section's replace accepts. Returns ids and versions for the outline, the page header fields and live-source flags.

linksA

Links of a note: 'out' (what it links to), 'in' (what links to it) or 'both', up to 3 hops. Each link has its source section, anchor, and whether it is broken or points outside the store.

log_queryA

Log entries filtered by time (since/until: ISO date or date-time, local time if no offset; until a date includes that day), op substring, page and task id; the newest limit matches, oldest first. include_tool adds the automatic tool events (writes, searches).

patch_sectionB

Edit one section. op: 'replace' (content = what read returned for the section, subsections included, headings relative), 'append' (after the subtree; may add subsections), 'prepend' (before the own text; no headings) or 'replace_own_text' (only the text before the first subsection; subsections kept; no headings). All but append need if_version (the section version read returned). On a page whose only section is the root, append and replace on the root can add headings. Optional summary updates the note's index line (on /index: the domain description). All or nothing, with the checks inside.

patch_headerA

Edit a note's page header: decision status, implementation status, evidence checked, verified_at (YYYY-MM-DD). if_version is the note version (read without a heading returns it). Fields left out keep their value; new evidence sets verified_at from its first date unless verified_at is given.

create_noteB

Create a new note (never overwrites) in an existing domain. body is markdown (text before the first heading is allowed). A project note needs a summary (its index line) and the page header (decision_status, impl_status, evidence). A working note (/working//…) needs neither and stays out of the index.

moveB

Rename a note within its domain; every link to it is rewritten in the same transaction (anchors kept). Moving a working note out of /working/ promotes it into project knowledge: owner only, and it needs a summary and, if it has none, the page header. Index, status, log and decisions pages do not move.

status_itemA

Add one status item (action='add', kind: state|open|blocker|next, text), change the text (and optionally the kind) of an open one (action='update', item_id, text) or close one (action='close', item_id). The status page and brief render from these items; the event keeps the old text. Owner only.

set_decision_statusA

Move a decision record through its life cycle by rewriting its one Status line: proposed -> accepted, rejected or superseded; accepted -> superseded (superseded_by must be an accepted decision) or void (an acceptance made in error; needs reason, which is added to the record as a Void reason line). Owner only.

log_appendB

Append a narrative log entry. The database stamps the time; pages must exist in the store.

preferenceA

Owner preferences layer. action='add' records how the owner wants work done (text) with the owner's own words (owner_quote, required); domain limits it to one domain, empty means everywhere. action='retire' (owner only) ends one by item_id. Every brief shows the active ones.

sourceA

Sources behind knowledge. action='add' registers or updates one (kind: snapshot, live, transcript (ref = run id or file), web, owner; verify_live=True means re-check the live system before acting on a copy) and, with path, cites it from that note. 'cite' / 'uncite' link an existing source to a note. Citing a verify_live source is refused while the note's verified_at is stale: refresh it with patch_header first.

leaseA

Claim a section (and its subsections) while drafting a long edit, for minutes (1–60, default 15). Other agents' writes to it, its subsections or its ancestors are refused until it expires or is released; your own patch_section releases it. action: 'take' or 'release'.

checkB

Read-only check of a domain: broken links and anchors, notes missing from the index, an index without its summary (the domain description), the same paragraph claimed in two notes, decision records without exactly one Status line, stale live sources. The same check runs inside every write and rolls the write back if it adds a problem.

batchA

Several writes in one transaction, all or nothing: ops = [{"tool": name, "args": {...}}, ...] with tools create_note, patch_section, patch_header, status_item, set_decision_status, log_append and source. Each op has its own role rules and refusals. The checks (and the pages that log_append names) run once, against the final state, so notes that link to each other can be created together. A refusal rolls back every op and gives op_index. Returns the result of each op.

create_domainA

Create a new domain with its start pages: index (with the catalog), status, log and decisions. description is the domain's line in list_domains: what it holds and when to choose it (e.g. "not for X; use Y"); it is kept as the index summary. domain: lowercase letters, digits and hyphens. Owner only.

list_domainsA

Every domain: its description (what it holds and when to choose it), note count, last log activity, and ops: true for the domain that records the memory system's own failures. Choose domains by description, then call brief. description_missing: true means the index has no summary; the first paragraph of the index stands in for it. preferences: the owner's active preferences for every domain (e.g. "No knowledge base for ": do not ask again to create one).

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

Disambiguation4/5

Most tools have clearly distinct purposes: read vs search, patch_section vs patch_header, log_query vs log_append, lease vs batch all differ in scope. Some residual overlap: patch_header's decision status field vs set_decision_status's Status line, and batch vs individual write tools could confuse an agent about which path to use. Descriptions are highly detailed and largely disambiguate these.

Naming Consistency3/5

Mixed conventions: bare verbs (move, brief, read, search, check, batch), verb_noun (log_query, patch_section, create_note, set_decision_status, create_domain, list_domains), and bare nouns (links, preference, source, lease, status_item). All are readable and snake_case throughout, but there is no single predictable pattern.

Tool Count4/5

19 tools is at the upper end for what the domain needs, but each maps to a distinct capability (notes, sections, headers, links, log, status, decisions, sources, preferences, leases, checks, batch). Nothing appears gratuitous, though the surface is slightly heavy.

Completeness4/5

Coverage is broad: create/read/update for notes, sections, headers, status items, decisions, sources and domains, plus search, links, log and validation. The notable gap is deletion/archival (no delete_note, delete_domain or link removal beyond uncite), which may be intentional for an auditable memory store but limits lifecycle completeness.