Skip to main content
Glama

get_journal

Retrieve recent journal entries from your knowledge base to review reflections, progress notes, and session handoffs, optionally filtering by start date.

Instructions

List journal entries from your knowledge base, newest first.

Use this to look back over your dated journal/log entries — reflections,
progress notes, and session handoffs — optionally from a given start date.
Helpful for "what was I working on lately?" and for rebuilding context at
the start of a session.

Args:
    date_from: Earliest entry date to include, as "YYYY-MM-DD". Empty
        string (the default) applies no date filter and returns the most
        recent entries.
    limit: Maximum number of entries to return, newest first. Defaults to 10.

Returns:
    A formatted list of journal entries with their dates, or a note if none
    match.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
date_fromNo
limitNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior3/5

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

No annotations are provided, so the description bears full burden. It states entries are returned newest first and optional date filtering, but lacks explicit read-only confirmation or discussion of rate limits/auth. Adequate but not rich.

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?

The description is well-structured: brief intro, usage context, parameter explanations. Every sentence adds value with no filler.

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?

Given the output schema exists, the description covers purpose, usage, and parameters. Minor missing details like pagination or exact return format, but overall complete for this simple tool.

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?

With 0% schema description coverage, the description fully explains both parameters: date_from format and behavior, limit meaning and default. Adds significant value beyond the schema.

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 clearly states it lists journal entries, newest first, which is a specific verb+resource. It distinguishes itself from sibling tools like add_journal_entry (adds) and other list tools.

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 provides explicit use cases: looking back over dated entries, rebuilding context. It does not explicitly say when not to use it or compare to alternatives, but the context is clear.

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/SVerITG/Metis_PH'

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