Engram

Overview Schema Source Related Servers Discussions Admin

get_daily_log

Read-onlyIdempotent

Read a project's daily log for a timestamped timeline of sessions with lesson and decision counts plus summaries. Call it when a new session needs a quick view of what happened on a given day.

Instructions

读取项目的每日日志（人类可读的会话时间线）。 / Read a project's daily log (human-readable session timeline).

用途：v3.30 新增——每次 wrap_up_session 会在 ``~/.engram/daily/<pid>/<YYYY-MM-DD>.md``
追加一条带时间戳的条目（含 lesson/decision/playbook 计数 + 摘要前 600 字符）。
新会话需要"上次到底干了什么"的快速概览时调本工具，比 search_knowledge 更直观。
Purpose (v3.30): every wrap_up_session appends a timestamped entry to
``~/.engram/daily/<pid>/<YYYY-MM-DD>.md`` with a lesson/decision tally
and the first ~600 chars of the summary. Call this when a new session
needs a glance-able "what happened today" timeline — faster than
search_knowledge for recall.

Args:
    project_folder: 项目文件夹路径。 / Project folder path.
    date: ISO 日期 ``YYYY-MM-DD``（可选，默认今天）。 / ISO date (optional, defaults to today).

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": {
      "project_folder": "<project_folder>"
    },
    "name": "get_daily_log"
  }
}

Input Schema

Name	Required	Description	Default
`date`	No
`project_folder`	Yes

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Addedv3.30.1May 27, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, closed-world), so the description's job is added context — and it delivers: it discloses the on-disk path, the entry format (timestamp + lesson/decision tally), and the ~600-char truncation of summaries, which tells the agent the content is lossy. It does not say what is returned when no entry exists for the requested date, which is the one behavioral gap.

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

Conciseness3/5

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

Content-wise it is front-loaded and every claim is relevant, but the entire description is duplicated in Chinese and English, roughly doubling length for the same information. Efficient in ordering, wasteful in volume.

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?

For a two-parameter read tool with an output schema (so return shape needs no explanation), the definition covers purpose, data source, entry format, and both parameters. The remaining gaps — empty/missing-log behavior and project_folder path resolution — are minor but real.

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 must carry the payload — and it documents both args: project_folder as a project folder path and date as ISO YYYY-MM-DD with a documented default of today. It stops short of specifying path form (absolute vs. relative) or invalid-date behavior.

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 a project's daily log / human-readable session timeline') and immediately explains the provenance: entries appended by wrap_up_session at a known path. It explicitly distinguishes itself from search_knowledge, so an agent can choose between the two without opening a 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 an explicit trigger ('when a new session needs a glance-able "what happened today" timeline') and names the alternative with a comparison ('faster than search_knowledge for recall'). The routing decision is fully specified.

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