Skip to main content
Glama
Sign In
everlog-mcp

everlog-mcp

by jlconlin
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

get_entry

Read-onlyIdempotent

Retrieve a journal entry by ID with full markdown text, date, tags, location, weather, AI summary, attachments, and optional photos for review or export.

Instructions

Get one entry in full: markdown text (attachments shown as placeholders such as [image a1b2c3d4], [audio a1b2c3d4 2:31]) plus date, modified time, journal, tags, location/coordinates/timezone, weather, bookmarked/pinned, word_count, the Everlog AI summary (if any) and an attachments list (attachment_id, type, size/duration, transcription). With include_images=true, up to max_images photos are returned as images after the entry.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "entry_id": "<entry_id>"
    },
    "name": "get_entry"
  }
}

Input Schema

NameRequiredDescriptionDefault
entry_idYes
max_imagesNo
include_imagesNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive behavior, so the bar is lower, but the description still adds real value by explaining that images are appended to the response when include_images=true and are capped by max_images. It also discloses that attachment content is represented as textual placeholders, which an agent otherwise wouldn't know.

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?

The core action is front-loaded in the first clause, and the long parenthetical field list is dense but each item is informative rather than filler. The image-return sentence is placed last, matching execution order.

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?

With no output schema, the description must describe the return shape and does so thoroughly, covering markdown body, metadata fields, AI summary, and the attachments list with its sub-fields. Minor gaps remain, such as placeholder fallback behavior and error handling for a missing entry_id, but the essential picture is complete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0%, so the description carries the burden, and it explains the two non-obvious parameters well: include_images controls whether photos are returned and max_images bounds the count. entry_id is only implied as identifying the single entry, leaving its expected format undocumented.

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?

The description opens with a specific verb and resource ('Get one entry in full') and immediately enumerates the payload, which separates it from list-oriented siblings like search_entries or list_journals. It never explicitly contrasts itself with a sibling, so it stops just short of a 5.

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?

Usage is implied rather than stated: an agent can infer this is the tool for retrieving a single entry's complete record rather than searching. There is no explicit 'use search_entries when you don't have an entry_id' routing, and no note on when fetching images is worth the cost.

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