Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault

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

CapabilityDetails
tools
{
  "listChanged": false
}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}
experimental
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
save_memoryA

Save a piece of context/memory for future conversations. Warns about likely duplicates (consider append_memory instead) and adds configured auto-tags.

Args: topic: Short title (e.g. "billing-api Postgres migration decision", "AAPL stock analysis") content: Detailed context to remember — include conclusions, data, links, action items category: One of: conversation, decision, incident, research, person, project, howto, config, other tags: Comma-separated tags (e.g. "postgres,database,billing") importance: One of: low, normal, high, critical source: Where this came from (default: the connected client's name, e.g. "claude-code") thread_id: Link related memories together with the same thread ID (e.g. "incident-2026-03-24") entities: JSON array of objects, e.g. [{"type":"service","value":"billing-api"},{"type":"person","value":"alice"}] expires_at: Optional expiry date (YYYY-MM-DD) after which this memory is less relevant

append_memoryA

Append additional context to an existing memory without replacing it. The new content is added with a timestamp separator. History is tracked.

Args: memory_id: The ID of the memory to append to content: New content to add (will be appended with a timestamp) source: Where this update came from (default: the connected client's name)

search_memoryA

Search memories by relevance: full-text search with stemming (topic and tag matches rank highest), falling back to substring matching. Returns a snippet per memory; use get_memory for the full text. Expired memories are excluded by default.

Args: query: Search query — plain words, hyphenated names, IDs, or FTS5 syntax (e.g. "tags:aws", "datadog OR sentry") category: Filter by category (optional) importance: Filter by minimum importance: low, normal, high, critical (optional) limit: Maximum number of results (default: 10, max: 100) include_expired: Set to true to include expired memories (default: false) full_content: Set to true to return full content instead of snippets (default: false)

list_memoriesA

List saved memories with optional filters. Expired memories excluded by default.

Args: category: Filter by category (optional) tag: Filter by tag (optional) thread_id: Filter by thread ID to see all related memories (optional) limit: Maximum number of results (default: 25, max: 200) include_expired: Set to true to include expired memories (default: false)

get_memoryB

Get the full content of a specific memory including linked entities and edit history.

Args: memory_id: The ID of the memory to retrieve

update_memoryA

Update an existing memory. Only provided fields are updated. Use append_memory to add context without replacing. Replaced content is kept in the memory's history (see get_memory_history).

Args: memory_id: The ID of the memory to update topic: New topic (leave empty to keep existing) content: New content (leave empty to keep existing) category: New category (leave empty to keep existing) tags: New tags (leave empty to keep existing) importance: New importance (leave empty to keep existing) thread_id: New thread ID (leave empty to keep existing) expires_at: New expiry (leave empty to keep existing)

delete_memoryB

Delete a memory and its linked entities.

Args: memory_id: The ID of the memory to delete

find_by_entityA

Find all memories linked to a specific entity (person, service, account, etc.).

Args: entity_type: Type of entity (e.g. "person", "service", "account", "bucket", "ticket") entity_value: Value to search, substring match (e.g. "alice", "billing-api", "prod-db") limit: Maximum results (default: 25, max: 200)

list_entitiesA

List all unique entities, optionally filtered by type. Useful to see what/who has been referenced.

Args: entity_type: Filter by type (optional, e.g. "person", "service")

get_threadA

Get all memories in a conversation thread, in chronological order.

Args: thread_id: The thread ID to retrieve (e.g. "incident-2026-03-24", "stock-analysis-march")

list_threadsA

List all conversation threads with their memory counts and latest activity.

get_daily_summaryA

Get memories created or updated on a specific local date, with new ones grouped by category.

Args: date: Date in YYYY-MM-DD format, in this machine's local timezone (default: today)

get_memory_historyB

Get the full edit/append history of a memory, including content replaced by update_memory.

Args: memory_id: The ID of the memory

cleanup_expiredA

Find and optionally delete expired memories.

Args: dry_run: If true (default), only lists expired memories without deleting. Set to false to actually delete.

find_duplicatesA

Find potentially duplicate memories. If topic is provided, finds memories similar to it. If no topic, finds groups of memories whose topics share most of their significant words.

Args: topic: Topic to check for duplicates (optional — if empty, scans all memories) limit: Maximum results or groups (default: 10, max: 100)

get_statsA

Get overview stats: total memories, breakdown by category, importance, top entities, active threads, expired count.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A3.8/5.0

Scored across 16 tools

Disambiguation4/5

Most tools target clearly distinct operations, and the descriptions actively disambiguate the tricky pairs (save vs append vs update, search vs list). The only soft overlaps are search_memory/list_memories/find_by_entity and find_duplicates vs search, but the parameter semantics (query vs filters vs entity) make the boundaries clear.

Naming Consistency5/5

All 16 tools follow a consistent snake_case verb_noun pattern (save_memory, get_thread, list_entities, find_duplicates, cleanup_expired). Verb families (get/list/find/search) are used predictably for their intent.

Tool Count4/5

16 tools is on the heavy side, but the memory domain genuinely spans CRUD, search, entities, threads, history, stats, and maintenance, and each tool maps to a real need. Slightly over the typical sweet spot without feeling padded.

Completeness5/5

Full lifecycle is covered: create (save), read (get/list/search), update (update/append), delete (delete_memory/cleanup_expired/delete linked entities), plus history, dedup detection, stats, threads, and entity lookup. No obvious dead ends for the stated purpose.

Maintenance

ActivityNo data
ResponsivenessNo issues