Skip to main content
Glama

mem_timeline

Read-onlyIdempotent

Show chronological context around a specific observation, listing preceding and following entries. Use it to understand the sequence of events and locate related memories.

Instructions

Show chronological context around a specific observation. Bodies come back as a 400-character preview marked content_truncated; read one in full with mem_get_observation.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
afterNoNumber of observations after the focus.
beforeNoNumber of observations before the focus.
projectNoAccepted for upstream schema compatibility; timeline is session-scoped.
observation_idYesObservation identifier at the center of the timeline. Also accepted as `id`, which is what the tools that fetch, pin or update one call it.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
afterNo
focusNo
beforeNo
after_totalNo
before_totalNoHow many of the session come before the focus, and how many after. `before` and `after` are capped by the window you asked for, so these say whether there is more on either side.
session_infoNo
Behavior5/5

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

Discloses key behavioral detail that bodies are returned as 400-character previews marked with `content_truncated`, and directs to mem_get_observation for full content. This adds value beyond the annotations which already declare read-only/idempotent hints.

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?

Two sentences: the first states the purpose concisely, the second discloses critical behavior and an alternative. No redundancy or extraneous information.

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

Completeness5/5

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

With a rich schema, annotations, and existing output schema, the description fully covers the tool's purpose, unique behavior, and usage boundaries. No significant gaps remain.

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% with detailed descriptions for each parameter (after, before, project, observation_id). The tool description adds no additional parameter-specific meaning, so baseline 3 applies.

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 uses a specific verb ('Show') and resource ('chronological context around a specific observation'), clearly distinguishing it from sibling tools like mem_get_observation (full read) and mem_search.

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 states when not to use this tool by directing users to mem_get_observation for full observation bodies, and implies the appropriate use case of viewing chronological context.

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/asanabrial/leteo'

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