Skip to main content
Glama
Sign In
everlog-mcp

everlog-mcp

by jlconlin
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

on_this_day

Read-onlyIdempotent

Retrieve journal entries from the same month and day in earlier years, ordered newest first with years-ago labels, to revisit past reflections on a chosen date.

Instructions

Entries written on the same month/day in earlier years, newest first, with years_ago. date: YYYY-MM-DD reference day (default: today in America/Denver); only years before it are included. Same result shape as search_entries.

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": "on_this_day"
  }
}

Input Schema

NameRequiredDescriptionDefault
dateNo
limitNo
journalNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare this a safe, idempotent, closed-world read, so the description doesn't need to re-establish that. It does add genuine behavioral detail: newest-first ordering, the years_ago field, the America/Denver default for 'today', and the rule that only strictly earlier years are included. What it omits is the effect of limit (truncation behavior) and journal scoping, which are real behavioral levers for a list tool.

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?

Three tight lines, front-loaded with what comes back and then the reference-date semantics, with no filler. The final sentence pointing at search_entries for the result shape is efficient reuse rather than wasted space. Slightly more could have been done with the same word budget by naming limit and journal behavior.

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

Completeness3/5

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

An output schema exists, so the description rightly avoids re-explaining the return structure and instead just cross-references search_entries. However, with three parameters at 0% schema coverage, leaving limit and journal entirely undocumented means an agent must guess at pagination size and journal filter semantics. Adequate for the date dimension, incomplete for the rest.

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 0%, so the description must carry parameter meaning, and it only partly does. It fully specifies the date parameter (YYYY-MM-DD format, timezone-aware default, prior-years-only filter) but says nothing about limit beyond the schema default of 50 or about which journal the journal parameter accepts.

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?

States specifically what is returned: entries sharing the same month/day from earlier years, ordered newest first, annotated with years_ago. That is a clear verb-plus-resource and implicitly distinguishes it from search_entries by the month/day matching rule. It stops short of an explicit 'use this, not that' framing, but the retrieval target is unambiguous.

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 through the 'same month/day in earlier years' scope and notes the result shape matches search_entries, which hints at the relationship. It never states when to prefer this over search_entries or how the two differ beyond output shape, and no exclusions are given. Guidance is implied rather than stated.

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

Deploy Server

Other Tools