Daily Journal
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| DAILY_JOURNAL_HOME | No | Directory where your data is stored: settings, editions, source records and the print ledger. Defaults to ~/.daily-journal. |
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": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| journal_statusA | Today's date in the reader's timezone, their settings, and whether today's edition is ready or already printed. Call this first. |
| save_settingsA | Update the reader's settings. Only known keys are accepted: title, timezone, print_time, latest_print_time, printer, paper, sides, copies, minimum_pages, topics, dateline_place, footer, hold_printing. Ask the reader before changing anything. |
| list_printersA | List the print queues on this computer and the system default. |
| get_layout_guideA | The layout rules and a complete sample edition. Read before writing an edition. |
| render_edition_pdfA | Lay out an edition and return every page as an image for visual review. Set live=true only for today's real edition; otherwise it is saved as a proof that can never print. Fix any reported overflow by shortening copy, then render again. |
| save_sourcesA | Save today's source record: story URLs, checked times, collection window, which inboxes and calendars were read, and anything that failed. Store summaries only, never message bodies, codes or passwords. |
| publish_editionB | Mark today's live edition ready for the morning print. Only after you have looked at every page. |
| print_editionA | Print today's ready edition. With send=false this only checks it and shows the print command. With send=true it prints once, inside the reader's print window. Never retry after an unclear result. |
| print_test_pageA | Print one test page to check the printer during setup. Requires confirm=true and the reader's go-ahead. |
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 9 tools
The staged workflow (render → publish → print) is clearly delineated by descriptions, and the read-side tools (journal_status, list_printers, get_layout_guide) each target a distinct artifact. The only mild overlap is print_edition vs print_test_page, which both invoke the printer but are differentiated by 'today's ready edition' vs 'setup test'.
Eight of nine tools follow a verb_noun pattern (save_settings, list_printers, render_edition_pdf, publish_edition, print_edition). The single exception is journal_status, which is noun-first, but it remains readable and predictable in context.
Nine tools is well-scoped for a daily-edition workflow, with each tool earning its place across status, configuration, layout, sourcing, rendering, publishing, and printing. Nothing feels redundant or padded.
The core daily lifecycle is covered end to end, including source provenance and a safe test-print path. Minor gaps exist: there is no way to list or retrieve past editions/proofs, and no retract/unpublish operation once an edition is marked ready.