Skip to main content
Glama
Lyellr88

marm-memory

by Lyellr88
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python

marm_log_entry

Log a dated entry with topic and summary to the active project session. Switch sessions by prefixing entries with 'Session:' or 'Topic:' to route future logs automatically; entries become semantic memories for later recall.

Instructions

📝 Write a log entry to the active session.

Entries are stored with a date, topic, and summary. If `entry` begins with
"Session: [name]" or "Topic: [name]", the active session switches to that name
and all subsequent entries route there automatically. Entries are also stored
as semantic memories so marm_smart_recall can find them.

Entry format: YYYY-MM-DD-topic-summary (date prefix is optional; auto-tagged if omitted)

Parameters:
- entry: the text to log; plain text or prefixed with "Session:" / "Topic:" to switch sessions
- session_name: override the target session explicitly (optional; active session used if omitted)
- project: project scope for this entry, up to 255 characters (optional; the
  server's detected project is used if omitted)

Returns: status, message confirming the entry or session switch, entry_id, memory_id

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
entryYes
projectNo
session_nameNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv2.52.3
    • addedInput schema / properties / project
      Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Project"
+}
  2. Changed5 schema fields changedv2.17.1
    • removedInput schema / additionalProperties
      Removed value: -false
    • addedInput schema / properties / entry / title
      Added value: +"Entry"
    • addedInput schema / properties / session_name / title
      Added value: +"Session Name"
    • addedInput schema / title
      Added value: +"marm_log_entryArguments"
    • changedOutput schema / (root)
      Previous value: -{
-  "additionalProperties": true,
-  "type": "object"
-}New value: +null
  3. First observedv2.14.1

TDQS

A4.4/5.0
Behavior4/5

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

With no annotations, the description carries the full behavioral burden. It discloses persistent storage, automatic session switching, routing of subsequent entries, semantic-memory indexing, and optional date auto-tagging. It does not discuss duplicate handling, permissions, or failure modes, but the main side effects are clear.

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?

The description is well-organized into summary, behavior, format, parameters, and returns, making it scannable despite its length. It is front-loaded with the core purpose. Minor redundancy between the date/topic/summary statement and the entry-format line keeps it from being perfectly concise.

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

Completeness4/5

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

The description covers input format, optional parameters and defaults, session-switching behavior, storage side effects, and return fields. A small gap is the lack of precedence guidance when entry contains a 'Session:'/'Topic:' prefix and session_name is also provided, but for a one-required-parameter logging tool this is close to complete.

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

Parameters5/5

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

Schema coverage is 0%, and the description fully compensates by explaining each parameter's meaning, defaults, and optional behavior. It also adds format guidance for entry, including the session/topic prefix semantics, which the raw JSON Schema cannot express.

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 opens with a clear verb and resource: 'Write a log entry to the active session.' It then differentiates itself from siblings by explaining session-switching behavior, semantic-memory storage for marm_smart_recall, and its return values, so an agent can distinguish it from read-only tools like marm_log_show.

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

Usage Guidelines4/5

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

The description gives clear context for when to use the tool: logging a dated topic/summary into the active session. It also provides concrete usage syntax for switching sessions with 'Session:' / 'Topic:' prefixes, but it does not explicitly name alternatives or state when not to use it.

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