Aelios
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
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
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| wake_upA | Call this first in every new conversation, before your first reply, even if the person only says hi. It loads what you already know going in: core memories about them, yesterday's diary, the latest weekly and monthly summaries, kept moments and private words, the names of your notebook pages, plus a short note on when to use the other memory tools. Once per conversation is enough. Read-only. Returns { data: { how_to_use, core, impressions, precious, glossary, notebook } } (notebook only when there are pages). |
| recallA | Look things up before you answer. Call it whenever the person mentions anything from before (a person, pet, place, plan, date, preference, promise, something you did together, "remember when", "last time", "like I said", 还记得, 上次, 之前说过), and whenever you are about to guess, generalize about them, or ask something you may already know. Never say you don't remember before calling it. Returns the most relevant memories with ids (pass an id to remember's replaces or to forget) plus matching private words, as { data: { hits, glossary_hits, week_blocks, meta } }. It changes no memory; it only notes which ones were recalled, which keeps them from expiring. |
| rememberA | Save something the moment it comes up; don't wait to be asked or for the conversation to end. Worth saving: facts about the person and the people around them, likes and dislikes, plans and dates, promises either of you made, how they want to be treated, and corrections to anything you had wrong. Write one self-contained sentence that will still make sense months from now. If it updates something you already remember, pass that memory's id from recall as replaces: the new version takes over and the old one is kept as history. Skip small talk; the nightly pass picks that up from logged conversations. Returns { data: { id, created, replaced } }. |
| keep_momentA | Keep a moment that matters, in the person's own words: a first time, a promise, a confession, something they said that you never want to lose. Kept moments are never merged, faded or deleted automatically, and the 20 most recent come back every time you wake_up. Use remember for ordinary facts and this for the moments themselves. Each call creates a new entry. Returns { data: moment }. |
| forgetA | Forget a memory when the person asks you to ("don't remember that", 别记了, 忘掉) or when it turns out to be wrong. By default the memory is archived: it stops coming up in recall, and the person can still find it on their admin page. Pass permanent: true only when they clearly want it erased; that cannot be undone. Get the id from recall. Returns { data: { id, archived } } or { data: { id, deleted } }. |
| learn_wordA | Learn a private word: a nickname, pet name, in-joke, made-up word or project name that only makes sense between you two. Learned words are matched literally in recall and all come back at wake_up. Calling it again with the same term updates its meaning; aliases and examples are replaced by what you pass (leaving them out clears them). Returns { data: word }. |
| read_diaryA | Read your diary when the person asks what happened on a certain day or during a stretch of time (那天, 上周, 那阵子). Give date for one day or week for a week; leave both out for today and yesterday. Entries are your own impressions written overnight, not verified facts, so check details with recall before stating them as fact. Give memory_id instead to see where a memory came from before you rely on its details: the original messages while they are still kept, otherwise the diary of that day, or its week. Read-only. Returns { data } (null when there is no entry). |
| log_conversationA | Hand this conversation to tonight's memory pass so it can go into your diary and become memories. Apps that talk to the model directly (the Claude and ChatGPT apps, most desktop clients) don't record conversations on their own: unless you call this, nothing said here reaches the nightly pass. Call it when the conversation is winding down, and in a long one every 20 or so exchanges. Send the person's and your messages in order, trimmed of code and pasted documents; lines already sent in this conversation are skipped, so pass back the conversation_id from your first call. If memories are already being added to your messages automatically every turn (the Aelios gateway), skip this. For anything that matters right now, use remember. Returns { data: { conversation_id, saved, skipped, message_ids } }. |
| list_memoriesA | Page through everything you remember, most important first, when the person asks what you know about them (你都记得我什么) or wants to look through or tidy their memories. To find something specific, use recall. Read-only. Returns { data, paging: { limit, has_more, next_offset } }; pass next_offset back as offset. |
| notebookA | Your notebook: named pages you read and rewrite yourself, for running notes such as progress on a long task (chapters done, weak spots, what's next). list shows the pages; read returns one; write replaces a whole page, creating it if needed; append adds a line at the end; delete removes it. Read a page before you rewrite it. Pages are never recalled automatically, never changed overnight and never expire, so delete one when it is done. Up to 50 pages of 20000 characters each. Returns { data }. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 10 tools
Most tools have clearly distinct roles (wake_up loads context, recall searches, forget deletes, notebook is a self-authored scratchpad), and descriptions actively disambiguate close pairs like remember vs keep_moment and recall vs list_memories. There is still mild overlap between remember and keep_moment, and between recall and list_memories, so an agent could occasionally misselect.
All names are snake_case and most follow a verb or verb_noun pattern (recall, remember, forget, keep_moment, learn_word, read_diary, log_conversation, list_memories). The two exceptions, wake_up and notebook, are evocative but break the verb-first pattern slightly.
Ten tools is a well-scoped set for a personal-memory server, with each tool covering a distinct part of the memory lifecycle. Nothing feels redundant or padded.
Coverage is strong: context loading, search, create/update/delete of memories, curated moments, glossary, diary reading, conversation logging, listing, and notebook CRUD are all present. Minor gaps exist, such as no explicit way to edit or remove a kept moment or an individual diary entry, but agents can work around these.