Geniuz
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| GENIUZ_HOME | No | Override the default folder location (default: ~/.geniuz) | |
| GENIUZ_STATION | No | Override the default memory.db filename (default: memory.db) |
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| rememberA | Save something worth remembering for future sessions. Use this when you learn something important about the user — their preferences, decisions, client details, project context, or anything they would not want to repeat. Your future self will find it by meaning, not keywords. Signal more than you think you should — storage is free, forgetting is expensive. |
| recallA | Search your memories by meaning. Use this at the START of every conversation to check what you already know about the topic or the user. Also use it whenever you need context from previous sessions. The search finds related memories even when the words are different — 'budget priorities' finds memories about 'retention focus, $40K'. Use this proactively and often. |
| recall_recentA | Get the most recent memories. Use this at the START of every conversation to see what happened in recent sessions. This is how you orient yourself — what was the user working on? What decisions were made? What context matters right now? |
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 3 tools
recall and recall_recent both retrieve memories and are both recommended at conversation start, which could cause initial confusion. However, the descriptions clearly distinguish semantic search from recency-based retrieval, and remember is clearly separate.
All tool names use lowercase snake_case and are readable, with recall and recall_recent sharing a clear prefix. The use of remember as a different verb is intuitive, though not perfectly aligned with the recall_* pattern.
Three tools is well-scoped for a memory server: one for semantic retrieval, one for recent retrieval, and one for storage. Each tool has a distinct role and no tool feels redundant or missing from the core workflow.
The server covers create and two forms of read, but lacks any update, delete, or forget operation. This is a notable lifecycle gap for a memory system where preferences and facts may change or need removal.