Skip to main content
Glama
Dakera-AI

dakera-mcp

Official
by Dakera-AI
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Rust
Remote

dakera_store

Persist agent memories (facts, decisions, context) with an importance score to control decay and retention.

Instructions

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.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
langNoen, de, fr, es, it, pt or nl (v0.12+)
tagsNoTags for filtering
contentYesMemory content text
agent_idYes
metadataNo
expires_atNoExpiry, Unix seconds (wins over ttl_seconds)
importanceNoImportance 0.0-1.0
session_idNoSession to associate with
memory_typeNo
ttl_secondsNoExpire after N seconds
attachment_refNosha256:<hex> uploaded to the agent's namespace (v0.12)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changedv0.11.0
    • addedInput schema / properties / attachment_ref
      Added value: +{
+  "description": "sha256:<hex> uploaded to the agent's namespace (v0.12)",
+  "type": "string"
+}
    • changedInput schema / properties / expires_at / description
      Previous value: -"Expiry Unix timestamp (seconds)"New value: +"Expiry, Unix seconds (wins over ttl_seconds)"
    • addedInput schema / properties / lang
      Added value: +{
+  "description": "en, de, fr, es, it, pt or nl (v0.12+)",
+  "type": "string"
+}
    • removedInput schema / properties / memory_type / description
      Removed value: -"Memory type (episodic|semantic|procedural|working)"
    • addedInput schema / properties / metadata
      Added value: +{
+  "type": "object"
+}
    • addedInput schema / properties / ttl_seconds
      Added value: +{
+  "description": "Expire after N seconds",
+  "type": "integer"
+}
  2. Addedv0.10.12
  3. Removedv0.10.11
  4. Addedv0.10.8

TDQS

C2.9/5.0
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, so the description carries the full burden. It mentions decay and the importance scale but omits critical behavioral details: whether this operation is idempotent, what permissions are needed, how conflicts are resolved, whether it returns the ID, or the implications of expiry fields.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Efficiently front-loaded with two sentences. The first states purpose, the second provides a key parameter default and guidance. No wasted words, though it could be slightly more structured with explicit usage notes.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With 11 parameters, no output schema, and no annotations, the description is incomplete. It covers purpose and one parameter but neglects critical behavior for a 11-param mutation tool: return values, error handling, alternative tools, and the semantics of fields like expires_at, ttl_seconds, and memory_type.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 73%, so the schema already documents most parameters including importance (0.0-1.0). The description adds context about importance defaults and recommended values, which is useful but limited to one parameter. Baseline 3 is appropriate given the high schema coverage.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb (persist) and resource (memory) with examples of memory content types (fact, decision, context). This clearly distinguishes it from read-oriented siblings like dakera_recall and dakera_search, though it doesn't name a specific alternative to avoid.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No explicit guidance on when to use this tool vs alternatives like dakera_forget or dakera_search. The description implies usage through its content examples but offers no exclusion criteria or alternative routing.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools