memkin

Add Timeline Entry

add_timeline_entry

Append a dated memory event to an existing page to record project progress, decisions, or notable events.

Instructions

add_timeline_entry

Append a dated memory event to an existing page.

When to use: record project progress, decisions, or notable events. When NOT to use: full page replacement; use put_page. Returns: ok plus slug/date/summary. On error: fix invalid date or find the correct page slug.

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": {
      "slug": "<slug>",
      "date": "<date>",
      "summary": "<summary>"
    },
    "name": "add_timeline_entry"
  }
}

Input Schema

Name	Required	Description
`date`	Yes	ISO date or datetime for the event.
`slug`	Yes	Existing page slug.
`detail`	No	Optional event detail.
`source`	No	Legacy display source string.
`summary`	Yes	Short event summary.
`provenance`	No	Optional SourceRef provenance object.

Output Schema

Name	Required	Description
`ok`	Yes	Whether the write succeeded.
`date`	Yes	Timeline event date.
`slug`	Yes	Page slug.
`summary`	Yes	Timeline event summary.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Jul 13, 2026

TDQS

A4.4/5.0

Behavior4/5

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

With no annotations provided, the description discloses the return shape ('ok plus slug/date/summary') and error handling. It implies mutation via 'append,' but lacks details on permissions or idempotency. Still, it provides key behavioral context.

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?

Very concise at 6 lines, structured with markdown headers. Every sentence adds value: action, usage, return, error. Front-loaded with the core purpose.

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 6 parameters, 3 required, an output schema, and no annotations, the description covers purpose, usage, error, and return. It omits details on optional parameters (detail, source, provenance) but the schema covers them. Adequate for an agent to use correctly.

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 coverage is 100%, so baseline is 3. The description does not add extra meaning beyond what the schema provides for parameters. It only references three required parameters in the return hint, without deeper explanation.

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 'Append a dated memory event to an existing page,' using a specific verb and resource. It distinguishes itself from the sibling tool `put_page` by specifying when not to use it ('full page replacement; use put_page').

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?

Explicitly provides when-to-use ('record project progress, decisions, or notable events') and when-not-to-use ('full page replacement; use put_page'). Includes error recovery guidance ('fix invalid date or find the correct page slug').

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