Skip to main content
Glama

Get journal entries

get_journal
Read-onlyIdempotent

Read the user's Habidu journal: one entry per day with their morning and/or evening answers (keyed by prompt, e.g. intention, gratitude, win, lesson), newest first. With no parameters it returns the 7 most recent entries; send date for one day, or from/to for a range of at most 31 days. Use it for reflection, weekly reviews or to recall what the user wrote; write entries with save_journal. Days with nothing written are left out; no entries returns count 0 with a note. Read-only.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_journal"
  }
}

Input Schema

NameRequiredDescriptionDefault
toNoRange end, YYYY-MM-DD, inclusive. Default: the user's local today.
dateNoOne day, YYYY-MM-DD, e.g. "2026-11-12". Do not combine with from/to.
fromNoRange start, YYYY-MM-DD, inclusive. Default: same as to.
limitNoHow many recent entries without date/from/to, 1-31. Default 7.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Annotations already cover read-only, idempotent, non-destructive and closed-world, so the extra bar is behavioral detail, and the description delivers it: results are newest first, days with nothing written are omitted, an empty result returns count 0 with a note, and ranges are capped at 31 days. The trailing 'Read-only' restates the annotation, but everything else adds real context an agent could not get from structured fields.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three sentences with no filler: what it returns, how to call it, then when to use it. The default behavior is front-loaded ahead of the parameter modes, which is the right order for an agent deciding whether to pass arguments at all.

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

Completeness5/5

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

There is no output schema, so the description carries the return-shape burden and does it: entry-per-day structure, prompt-keyed answers, newest-first ordering, gap skipping, and the empty-result contract. For a four-parameter read tool with full annotation coverage, nothing an agent needs to call it correctly is missing.

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?

Schema description coverage is 100%, so the schema already documents date, from, to and limit including the YYYY-MM-DD format and the 'do not combine' rule. The description reinforces the mode selection and the 31-day cap but adds no format or edge-case meaning the schema lacks, so the baseline 3 applies.

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?

States a specific verb and resource ('Read the user's Habidu journal') and immediately defines the shape of what comes back: one entry per day with morning/evening answers keyed by prompt, newest first. It also names the sibling it is not ('write entries with save_journal'), so an agent can distinguish it from the write path without opening either schema.

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

Usage Guidelines5/5

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

Gives explicit use cases ('reflection, weekly reviews or to recall what the user wrote') and routes the write case to save_journal. It also states the default call behavior (no parameters = 7 most recent) and the selection rule for the other modes (date for one day, from/to for a range), which is the decision an agent actually has to make.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources