Skip to main content
Glama

Metis ยท Memory Curator โ€” List Recent Sessions

list_recent_sessions

Retrieve recent session summaries with key topics and decisions to continue previous conversations or review past work.

Instructions

List the most recent session summaries, newest first.

Returns the rolling history of saved session summaries so you can pick up
where a previous conversation left off or review recent decisions and
topics. Each entry carries its summary, key topics, and decisions.
Complements search_session_memory (keyword search) and
save_session_summary (which writes these rows).

Args:
    limit: Maximum number of summaries to return, most recent first
        (default 20).

Returns:
    A list of session-summary dicts (id, session_id, summary, key_topics,
    decisions, created_at); a single-item list with an "error" key on failure.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior3/5

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

No annotations are provided, so the description carries full burden. It discloses the return format (list of dicts with specific keys) and error case (single-item error list). However, it does not mention any additional behavioral traits like rate limits, authorization requirements, or side effects. For a simple list operation, this is adequate but not exceptional.

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 concise at around 150 words, with clear sections (purpose, usage, args, returns). Every sentence adds value, and there is no repetition of schema or annotations.

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?

Given low complexity (one optional parameter), no annotations, and an output schema, the description is complete. It covers purpose, usage context, parameter semantics, return structure, and error handling. It also references sibling tools for comparison.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The only parameter is 'limit,' with type integer, default 20. The description adds meaning: 'Maximum number of summaries to return, most recent first (default 20).' Since schema description coverage is 0%, the description fully compensates by explaining default behavior and ordering.

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 'List the most recent session summaries, newest first.' It specifies the verb (list), resource (session summaries), and ordering (newest first). It distinguishes from sibling tools by mentioning complementary tools like search_session_memory and save_session_summary.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description explains when to use this tool, such as 'to pick up where a previous conversation left off or review recent decisions and topics.' It also notes that it complements search_session_memory and save_session_summary, providing context for selection. While it lacks explicit when-not-to-use guidance, the context is clear.

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/SVerITG/Metis'

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