Skip to main content
Glama
Sign In
dakera-mcp

dakera-mcp

Official
by Dakera-AI
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Rust
Remote

dakera_session_start

Open a memory session that groups stored memories under a session_id. Start one per agent so stored memories stay organized and end automatically after idle time.

Instructions

Open a session; its session_id groups the memories you store. The server ends a session idle for 4 h by default (v0.12.2+).

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "agent_id": "<agent_id>"
    },
    "name": "dakera_session_start"
  }
}

Input Schema

NameRequiredDescriptionDefault
agent_idYes
metadataNoOptional session metadata
idle_timeout_secsNoEnd after this many idle seconds; 0 = never (v0.12.2+)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.12.3
    • addedInput schema / properties / idle_timeout_secs
      Added value: +{
+  "description": "End after this many idle seconds; 0 = never (v0.12.2+)",
+  "type": "integer"
+}
  2. Addedv0.10.12
  3. Removedv0.10.11
  4. Addedv0.10.8

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations provided, the description carries the full behavioral burden, and it does disclose one valuable trait: idle sessions are auto-ended after 4 h by default. It omits other important behaviors — whether calling again for the same agent_id creates a duplicate session, what the call returns, and any permission or concurrency effects.

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

Conciseness5/5

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

Two compact clauses with zero filler; the core purpose is front-loaded and the lifecycle caveat follows immediately. Every phrase contributes information.

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

Completeness3/5

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

With no annotations and no output schema, the description should say more about the return shape (presumably the session_id) and what happens on repeated calls. It implies session_id is returned and covers lifecycle, but leaves the required agent_id and duplicate-session semantics unexplained.

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 coverage is 67%, with agent_id (the required param) undocumented in both schema and description, while metadata is covered by the schema and idle_timeout_secs gets the useful extra detail that 0 means never. The description adds the 4 h default behavior but does not explain the required identifier.

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 and resource ('Open a session') and immediately explains its function relative to siblings: the session_id groups memories you store, which distinguishes it from dakera_store/dakera_session_end. It stops short of naming the counterpart tool explicitly, but the agent can place it correctly.

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

Usage Guidelines3/5

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

The linkage to storing memories implies this is a prerequisite step before dakera_store, and the idle-timeout note hints at lifecycle expectations. However, there is no explicit 'use this when...' or 'do not use if a session already exists' guidance, and no mention of how it relates to dakera_session_end.

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