Skip to main content
Glama

list_recent_sessions

Retrieve the most recent session summaries to review past conversations, topics, and decisions. Pick up where you left off or catch up on recent research activity.

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?

With no annotations provided, the description must disclose all behavioral traits. It describes the return format, error handling, and ordering (newest first). However, it does not mention whether the tool is read-only, any performance considerations, potential side effects, or authentication requirements.

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 well-structured: a clear first sentence defining the action, followed by contextual use, then formatted Args and Returns sections. Every sentence adds value with no redundancy.

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 the tool's simplicity (one optional parameter, clear output described in Returns), the description covers input, output, usage, error handling, and ordering. No gaps are apparent.

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 single parameter 'limit' is described in the Args section: 'Maximum number of summaries to return, most recent first (default 20).' This adds meaning beyond the schema, which only specifies type and default, and the schema description coverage was 0%.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool lists recent session summaries in reverse chronological order. It also mentions the content of each entry (summary, key topics, decisions). However, it does not explicitly distinguish from the sibling 'list_recent_memory' tool, though it does differentiate from '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 the tool: to review recent conversations or decisions. It also notes that it complements keyword search and writing tools, providing some guidance on alternatives. However, it lacks explicit exclusion criteria or when not to use it.

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