saihm-memory
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| SAIHM_AUTH_HEADER | No | Authorization header value (e.g., 'Bearer <JWT>') for SAIHM endpoint. | |
| SAIHM_ENDPOINT_URL | No | Endpoint URL for SAIHM hosted memory. Default is local sandbox. | |
| SAIHM_MASTER_SECRET_HEX | No | 64 hex character master secret for client-side encryption. |
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 |
|---|---|
| saihm_rememberA | Store a memory in SAIHM (sealed client-side before it leaves this process). Pass cellId to update an existing memory. |
| saihm_recallA | Recall SAIHM memories (decrypted client-side), optionally filtered by a keyword. |
| saihm_forgetA | Permanently crypto-shred a memory by cellId (irreversible; GDPR Art. 17 erasure). |
| saihm_statusA | Non-custodial status: tier, active memory count, and custody (no plaintext). |
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 4 tools
Each tool has a clear, non-overlapping function: storing, recalling, deleting, and checking status of memories. There is no ambiguity about which tool to use for a given operation.
Three tools use a consistent verb pattern (remember, recall, forget), while 'status' is a noun, which is a slight deviation. However, the common 'saihm_' prefix and predictable naming keep it coherent.
Four tools is well-scoped for a memory management system: create/update, read, delete, and status. Each tool serves a distinct and necessary purpose without redundancy.
The toolset covers the full lifecycle of memories: remember (create/update), recall (read with optional filtering), forget (delete), and status (overview). There are no obvious gaps for the domain.