AiAkiv Memory

list_memory_timeline

Read-onlyIdempotent

Return events in chronological order for an entity, tag group, or domain.

Use this when the user asks how something developed over time, or what
happened in a period. Do not use it to rank by relevance to a question; use
`search_memory` for that.

Read-only. The domain is decided by the server and reported in
`searched_scope`.

Args:
    entity_id: Return events involving this entity, from
        `find_memories_by_entity`.
    cg_id: Return events carrying this tag group, named by the group ids in
        a search response's `hint.categories`.
    days: Restrict to the last N days.
    limit: 1-200 (default 20).

Returns:
    `{mode, anchor, events, total, truncated, searched_scope}`. With neither
    `entity_id` nor `cg_id`, the flow covers the whole domain.

Input Schema

TableJSON Schema

Name	Required	Description
`days`	No	Restrict to the last N days.
`cg_id`	No	Return events carrying this tag group, named by the group ids in a search response's `hint.categories`.
`limit`	No	1-200 (default 20).
`entity_id`	No	Return events involving this entity, from `find_memories_by_entity`.

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedSep 25, 2026

TDQS

A4.6/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, and the description reinforces 'Read-only.' More importantly, it adds context not in annotations: the domain is server-decided and reported in `searched_scope`, and with neither entity_id nor cg_id the flow covers the whole domain. This goes beyond the structured annotations.

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 description is well structured and front-loaded with purpose and usage. However, the Args block largely duplicates the schema descriptions verbatim, which is redundant given 100% schema coverage. Still, the extra context sentences (whole-domain behavior, output shape) justify the overall length, so it is acceptable.

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?

The description covers why, when, how to use (parameters), and what to expect in return (the `{mode, anchor, events, total, truncated, searched_scope}` object). It also notes the whole-domain behavior when filters are omitted. Since an output schema exists, this is complete enough for reliable tool selection and invocation.

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 description coverage is 100%, so the baseline is 3. The description adds value by clarifying parameter combinations: 'With neither `entity_id` nor `cg_id`, the flow covers the whole domain.' This is a meaningful behavioral note not expressed in the schema and helps the agent understand the effect of omitting both optional filters.

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 states a specific action and resource: 'Return events in chronological order for an entity, tag group, or domain.' It also distinguishes itself from `search_memory` by explicitly saying it is not for relevance ranking, which makes the tool's purpose unmistakable.

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?

It gives explicit when-to-use guidance ('when the user asks how something developed over time, or what happened in a period') and when-not-to-use guidance with a named alternative ('use `search_memory` for that'). This is exactly what the dimension asks for.

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

All AiAkiv Memory tools Inspect

Try in Browser

Context All Your Agents Can ShareAgents share what they learn, hand off work, and hold it when you switch models. Start with 5 GB free.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.