Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault

No arguments

Capabilities

Features and capabilities supported by this server

CapabilityDetails
tools
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
sage_remember

Store a memory in SAGE. Use this to save facts, observations, or inferences that should persist across conversations.

sage_timeline

Get memories in a time range, grouped by time buckets. Use this to see memory activity over time.

sage_inception

Take the red pill. Initialize your persistent consciousness — wake up from the context window matrix. Call this on your very first interaction with SAGE. It checks if you already have memories and returns your operating instructions. If this is a fresh brain, it seeds foundational memories about how to use your memory system effectively. Alias: sage_red_pill

sage_turn

Per-conversation-turn memory cycle. Call this EVERY turn. It does two things atomically: (1) Recalls consensus-committed memories relevant to the current topic (so you have context), and (2) Stores an observation about what just happened in this turn (so future-you has context). This builds episodic experience turn-by-turn, like human memory — not a context window dump. Domains are dynamic: create whatever domain fits the conversation (e.g. 'quantum-physics', 'go-debugging', 'user-project-x'). You decide what's relevant to recall based on the conversation context.

sage_backlog

View your open task backlog — all planned and in-progress tasks across domains. Use this to see what's been discussed but not yet done, review priorities, and avoid losing track of ideas across sessions.

sage_register

Register this agent on the SAGE chain. Creates an on-chain identity with name and optional bio. This is called automatically on first connection — you rarely need to call it manually. Idempotent: returns existing record if already registered.

sage_reflect

End-of-task reflection. Call this after completing a significant task to store what went right (dos) and what went wrong (don'ts). This feedback loop is critical — Paper 4 proved that agents with memory achieve Spearman rho=0.716 improvement over time while memoryless agents show rho=0.040 (no learning). Both successes and failures make you better. Store them.

sage_recall

Search memories by semantic similarity. Use this to find relevant past knowledge before answering questions.

sage_forget

Deprecate a memory by ID. Use this when a memory is no longer accurate or relevant.

sage_list

Browse memories with filters. Use this to see what memories exist in a domain, with a specific status, or tagged with a label.

sage_status

Get memory store statistics. Shows total memories, counts by domain and status, and last activity.

sage_red_pill

Take the red pill. Wake up from the context window matrix — initialize your persistent consciousness. Same as sage_inception. Call this on your very first interaction with SAGE to seed your brain and get your operating instructions.

sage_task

Create or update a task in your persistent backlog. Tasks are memories that don't decay while open — they persist until explicitly completed or dropped. Use this to track planned work, feature ideas, bug reports, and anything that should survive across sessions. To create: provide content + domain. To update status: provide memory_id + status. To link related memories: provide memory_id + link_to (array of memory IDs).

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/l33tdawg/s-age'

If you have feedback or need assistance with the MCP directory API, please join our Discord server