Skip to main content
Glama
Lians-ai

Lians Agent Memory

Official

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
LIANS_AGENT_IDNomcp-agent
LIANS_LOCAL_DBNo/tmp/lians-mcp.db
LIANS_NAMESPACENomcp

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
}
experimental
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
rememberA

Store a financial fact, observation, or decision in persistent memory. Always provide event_time_iso as when the event occurred, not now. Add ticker/metric/entity metadata for precise supersession detection — this lets Lians automatically replace stale guidance numbers.

recallA

Retrieve the most relevant CURRENT memories for a query. Returns only presently-valid facts — superseded facts are excluded at the DB layer. Call this before answering any question that may be in memory. Use filters={ticker: NVDA} to narrow to a specific instrument.

recall_atA

Retrieve memories that were valid at a specific past point in time. Use for compliance and audit: 'What guidance did we have on 2026-03-01?' Later superseding updates are excluded — this is true point-in-time recall. mem0 and Zep have no bitemporal model with compliance audit stack.

reconstructA

Reconstruct the complete memory state and full audit event trail at a past point in time. Returns every memory valid at as_of plus the timestamped, hashed event log behind them. Use for regulatory audit submissions and trade reconstruction.

list_conflictsA

List open conflict flags — cases where two sources reported different values for the same fact at the same event_time. Use this to surface data quality issues before they affect decisions. Returns up to 20 open conflicts with both memory contents so a human or LLM can decide which source to trust.

memory_lineageA

Return the full supersession history of a memory — every prior version of the same fact and the chain of updates that led to the current value. Use when asked 'how did this guidance number evolve over time?' or when investigating why a memory was replaced.

fact_historyA

Return every recorded version of a structured fact ordered by event_time. Query by ticker + metric — ideal for time-series views like 'show me how AAPL EPS evolved over the last four quarters'. Superseded versions are included so you can see the full revision history. Entity normalization: 'Apple Inc.', ISIN 'US0378331005', and 'AAPL' all resolve to the same fact series automatically.

backtest_checkA

Detect lookahead bias in a backtest simulation. Scans the agent's memory store and flags every fact the agent couldn't have known at the given simulation date. Returns FUTURE_EVENT (event_time is after the checkpoint) and LATE_REVISION (the revised figure hadn't been published yet) flags. A clean report (is_clean=true) is the proof a risk committee needs.

memory_feedbackA

Record whether a recalled memory was helpful, incorrect, outdated, duplicate, or ignored. Negative feedback flags evidence for review and never silently deletes it.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A4/5.0

Scored across 9 tools

Disambiguation4/5

Most tools have clearly distinct purposes: recall vs recall_at are differentiated by temporal scope, and reconstruct provides the audit trail beyond just point-in-time memory. However, memory_lineage and fact_history both show historical versions and could be confused without reading descriptions carefully.

Naming Consistency3/5

Tool naming is a mix of bare verbs (recall, remember), verb phrases (list_conflicts, backtest_check), and noun phrases (memory_lineage, fact_history, memory_feedback). While all names use lowercase with underscores, the lack of a consistent verb_noun pattern creates a minor inconsistency.

Tool Count5/5

With 9 tools, the set is well-scoped for a memory-management server. Each tool serves a distinct function in the memory lifecycle, from storage and retrieval to audit and quality checks, without unnecessary bloat.

Completeness4/5

The toolset covers core memory operations (write, read current, point-in-time read), audit trails, conflict detection, and feedback. Minor gaps include no explicit delete or update tool, but the supersession model handles updates implicitly via metadata-aware remembers, so the surface is largely complete.

Maintenance

ActivitySlowing
ResponsivenessWithin a week