log-reflect-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| RECORDS_REPO_PATH | Yes | Absolute path to the records repository (log-reflect-practice) | |
| RECORDS_TIME_ZONE | No | Time zone for the records, e.g., America/Los_Angeles |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| capture_journalB | Create or append a personal journal fragment. Supply lightly edited content that preserves the user's words and uncertainty. |
| capture_inputC | Save an external input such as an article, book, podcast, video, course, or conversation as a Markdown note. |
| get_records_by_date_rangeA | Read journal and input records within an inclusive date range. |
| search_recordsC | Search journal and input Markdown files for matching text. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 4 tools
Each tool has a unique, non-overlapping purpose: capturing journal entries vs. external inputs, and reading by date vs. searching by text. The boundaries are clear, and an agent would rarely misselect between them.
All tools use a consistent snake_case verb_noun pattern. 'get_records_by_date_range' is slightly longer but still follows the same style as 'capture_journal' and 'search_records', with no mixed conventions.
With 4 tools, the server is well-scoped for its purpose of logging and retrieving reflections. Each tool serves a necessary function, and the count is neither too thin nor bloated.
The set covers the core capture and retrieval workflows for journaling and external inputs. Minor gaps exist (e.g., no explicit update/delete, no single-record get by ID), but agents can work around these via search and date-range queries.