Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
DAKERA_API_KEYYesYour Dakera API key.
DAKERA_API_URLYesThe URL of the Dakera API server.
DAKERA_MCP_PROFILENoThe profile controls which tools appear in tools/list (core. admin, power or all).

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

Tools

Functions exposed to the LLM to take actions

NameDescription
dakera_storeC

Persist a memory (fact, decision, context) for an agent. importance defaults to 0.5; use 0.8-1.0 for memories that must survive decay.

dakera_recallB

Semantic recall: the top_k (default 5) memories closest to a query, optionally narrowed by tags, memory_type or session_id. include_associated adds KG neighbours one hop away (dakera_recall_associated goes deeper).

dakera_forgetA

Permanently delete memories by ID or tag. Provide memory_ids for exact removal or tags to bulk-delete all memories sharing those tags. Deletion is immediate and irreversible — prefer dakera_memory_importance to suppress without deleting.

dakera_batch_recallA

List memories by filters (tags, importance, time window, type, session) without a query; at most limit (default 100). Use instead of dakera_recall when no semantic search is needed.

dakera_batch_forgetA

Bulk-delete memories matching filters (tags, importance range, time window, type, session); at least one is required. Permanent: to demote instead, use dakera_memory_importance.

dakera_searchA

Semantic search with optional tag and memory-type pre-filters. Prefer over dakera_recall when results must be constrained by tag or type alongside the semantic match.

dakera_session_startA

Open a new session, returning a session_id that groups stored memories under a shared context. Attach metadata such as task type or trigger source for later retrieval.

dakera_session_endA

Close an active session with an optional summary. Always call at run end (even on error) to avoid orphaned sessions; summary is retrievable via dakera_session_get.

dakera_knowledge_graphA

Build a knowledge graph from a seed memory using embedding similarity. Use to explore how a concept connects to stored knowledge. For BFS traversal of an existing linked graph use dakera_graph_traverse.

dakera_fulltext_searchA

BM25 keyword search over indexed documents. Use over vector search when exact-term recall matters (error codes, IDs, names). For semantic+keyword combined use dakera_hybrid_search.

dakera_hybrid_searchA

BM25 + vector ANN hybrid search in a single pass. Omit vector for BM25-only mode. Use for RAG when pure semantic or keyword search alone is insufficient. vector_weight: 0.0=BM25, 1.0=vector (default 0.5).

dakera_extractA

Extract entities, topics, key phrases and a summary from text with the provider chain: extractor_override, then the namespace default, then the server default (GLiNER local). For ad-hoc GLiNER types use dakera_auto_tag. Needs a write key for the namespace (for all namespaces when neither namespace nor agent_id is given).

dakera_discover_toolsA

Search the Dakera tool catalog by keyword or tier (core/power/admin/meta) and return names and one-line summaries without loading full schemas. Call this first to find relevant tools, then use dakera_load_tools to fetch only the schemas you need — avoids loading the full catalog upfront.

dakera_load_toolsA

Fetch the full inputSchema for one or more named tools. Use after dakera_discover_tools. Returns schemas for found tools and a not_found list for unrecognized names.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A3.6/5.0

Scored across 14 tools

Disambiguation3/5

Multiple search tools (dakera_recall, dakera_batch_recall, dakera_search, dakera_fulltext_search, dakera_hybrid_search) overlap in purpose, and dakera_forget/dakera_batch_forget share tag-based deletion. Descriptions help differentiate them, but an agent may still hesitate when choosing between semantic, keyword, hybrid, and filter-only retrieval.

Naming Consistency4/5

All tools use snake_case with a consistent dakera_ prefix, and most follow a verb_noun pattern (store, extract, recall, forget, session_start). Minor deviations like dakera_knowledge_graph and dakera_fulltext_search are noun phrases, but the overall convention is predictable.

Tool Count4/5

With 14 tools, the server is well within a reasonable range for memory and knowledge management. It covers CRUD, search, sessions, graph exploration, and meta-tool discovery, though the several search variants and meta tools make it slightly heavy.

Completeness3/5

Core lifecycle operations exist (store, recall/search, forget), but there is no update/upsert tool for memories or get-by-ID retrieval. Descriptions reference absent tools such as dakera_memory_importance and dakera_recall_associated, indicating notable gaps for a memory server.

Maintenance

ActivityMaintained
ResponsivenessUnresponsive