Skip to main content
Glama
Lyellr88

marm-mcp

marm_log_entry

Write date-stamped entries to the current session. Switch sessions by starting the entry with 'Session: [name]' or 'Topic: [name]'.

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.

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)

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

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
entryYes
session_nameNo
Behavior4/5

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

Since no annotations are present, the description carries full burden. It transparently discloses session-switching behavior, auto-tagging of dates, and return fields (status, message, entry_id). It does not cover error conditions or limitations, but the key behaviors are well explained.

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-structured with an emoji header, clear purpose, and bulleted parameter list. It is front-loaded but repeats the entry format slightly (in both prose and the 'Entry format' line). Very concise overall.

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 purpose, parameters, return values, and the critical session-switching behavior. It lacks mention of error conditions and does not reference sibling tools like marm_log_show for related operations. For a tool of this complexity, coverage is strong.

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?

The description provides rich semantics for both parameters, explaining the entry format, session-switching prefixes, and the override behavior of session_name. This compensates for the complete lack of schema descriptions (0% 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?

The description clearly states the tool's purpose ('Write a log entry to the active session') and explains session switching behavior. However, it does not explicitly differentiate from sibling tools like marm_log_show, which readers would compare against.

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 description implies usage for logging entries but provides no explicit guidance on when to use this tool versus alternatives (e.g., marm_log_show for reading) or when not to use it. No exclusion criteria are provided.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Lyellr88/marm-memory'

If you have feedback or need assistance with the MCP directory API, please join our Discord server