Skip to main content
Glama

get_timeline

Retrieve activity blocks and screen-context metadata for one local calendar day, oldest first, with pagination via an after cursor. Use it to review what happened on a given day within local work memory.

Instructions

Get activity blocks and screen-context metadata for one local calendar day, oldest first. No pixels or encrypted file paths are returned. A list cut at the limit sets activity_truncated or screenshots_truncated; call again with after set to its last ended_at or captured_at to continue. Requires the separate screen-memory permission.

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

Input Schema

NameRequiredDescriptionDefault
dayNoLocal calendar day (YYYY-MM-DD); defaults to today.
afterNoOptional ISO 8601 time; return only what follows it within the day.
limitNoMaximum activity blocks and screenshots (default 200, maximum 500).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.4/5.0
Behavior5/5

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

With no annotations provided, the description carries the full behavioral burden and does so well: it discloses privacy-relevant return exclusions (no pixels or encrypted paths), truncation flags, how to paginate using after with last ended_at or captured_at, and the separate screen-memory permission requirement. These are concrete operational traits an agent needs before calling.

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?

The description is four tight sentences arranged from purpose to return constraints to pagination to permission. Every sentence adds a distinct operational detail, and the main purpose is front-loaded.

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 read-only timeline tool with three optional parameters, no output schema, and no annotations, the description covers most needs: what is returned, what is excluded, pagination behavior, and permissions. It does not detail the fields inside activity blocks or screen-context metadata, but that is a minor gap for this tool's complexity.

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 100%, so the baseline is 3, but the description adds meaningful semantics by explaining that after should be set to the last ended_at or captured_at when a truncation flag is present. It also reinforces day scoping and oldest-first ordering, though it does not elaborate on limit beyond what the schema states.

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 names a specific verb and resource: get activity blocks and screen-context metadata for one local calendar day, ordered oldest first. It distinguishes itself from screenshot-oriented siblings by stating that no pixels or encrypted file paths are returned, and its day-scoped timeline scope differentiates it from recent-activity tools.

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 this is the tool for retrieving a day's timeline but does not explicitly name alternatives or state when not to use it. It does provide useful continuation guidance for pagination, but alternative selection is left to inference.

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