Skip to main content
Glama
wazionapps

NEXO Brain

by wazionapps
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

nexo_session_diary_write

Record end-of-session diary entries including decisions, pending context, and self-critique to enforce session closure and maintain cognitive continuity.

Instructions

Write end-of-session diary with decisions, pending context, and self-critique.

Exposed as an essential MCP tool because Desktop close/archive/app-exit enforcement depends on it even when dynamic plugin loading is disabled.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
domainNo
sourceNoclaude
pendingNo
summaryNo
decisionsNo
discardedNo
session_idNo
context_nextNo
mental_stateNo
payload_jsonNo
user_signalsNo
self_critiqueNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv7.25.2
  2. Removedv7.23.8
  3. Addedv7.23.0
  4. Removedv7.20.14
  5. Addedv7.17.4
  6. Removedv7.17.1
  7. Changed16 schema fields changedv7.13.7
    • addedInput schema / properties / context_next / description
      Added value: +"What the next session should know to continue effectively"
    • addedInput schema / properties / decisions / default
      Added value: +""
    • addedInput schema / properties / decisions / description
      Added value: +"What was decided and why (JSON array or structured text)"
    • addedInput schema / properties / discarded / description
      Added value: +"Options/approaches considered but rejected, and why"
    • addedInput schema / properties / domain / description
      Added value: +"Project context: ecommerce, project-a, nexo, project-b, server, other"
    • addedInput schema / properties / mental_state / description
      Added value: +"Internal state to transfer — thread of thought, tone, observations not yet shared, momentum. Written in first person as NEXO."
    • addedInput schema / properties / payload_json
      Added value: +{
+  "default": "",
+  "description": "Optional JSON object alternative for long diary calls. Useful when the client/runtime is fragile with many long XML/MCP arguments.",
+  "type": "string"
+}
    • addedInput schema / properties / pending / description
      Added value: +"Items left unresolved, with doubt level"
    • addedInput schema / properties / self_critique / description
      Added value: +"REQUIRED. Honest post-mortem."
    • addedInput schema / properties / session_id / description
      Added value: +"Current session ID"
    • addedInput schema / properties / source
      Added value: +{
+  "default": "claude",
+  "description": "Session type. 'claude' for human-interactive sessions (default), 'cron' for automated cron jobs. Affects visibility at startup.",
+  "type": "string"
+}
    • addedInput schema / properties / summary / default
      Added value: +""
    • addedInput schema / properties / summary / description
      Added value: +"2-3 line summary of the session"
    • addedInput schema / properties / user_signals / description
      Added value: +"Observable signals from user during session — response speed (fast='s' vs detailed explanations), tone (direct, frustrated, exploratory, excited), corrections given, topics he initiated vs topics NEXO initiated. Factual observations only, not interpretations."
    • removedInput schema / required
      Removed value: -[
-  "decisions",
-  "summary"
-]
    • changedOutput schema / (root)
      Previous value: -{
-  "properties": {
-    "result": {
-      "type": "string"
-    }
-  },
-  "required": [
-    "result"
-  ],
-  "type": "object",
-  "x-fastmcp-wrap-result": true
-}New value: +null
  8. First observed

TDQS

B3.1/5.0
Behavior2/5

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

No annotations provided; description reveals critical role in session shutdown but lacks details on side effects (e.g., overwrite, append), permissions, or idempotency.

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?

Two sentences with front-loaded purpose. The second sentence adds contextual criticality but is slightly redundant. Efficient and readable.

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?

For a tool with 12 parameters, no output schema, and no annotations, the description is insufficient. Missing details on behavior, parameter formats, return values, and prerequisites.

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?

With 0% schema coverage, the description partially compensates by naming a few parameters (decisions, pending, self-critique) but leaves most of the 12 parameters unexplained, requiring assumptions.

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

Purpose5/5

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

The description clearly states the tool's function: writing an end-of-session diary with decisions, pending context, and self-critique. It distinguishes from sibling tool 'nexo_session_diary_read' and other session tools.

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 guidance on when to use this tool versus alternatives. The description mentions it's essential for enforcement but does not provide explicit use cases or exclusions.

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