Skip to main content
Glama
Sign In
Session Memory

Session Memory

by Bhavanachowdary18
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

list_sessions

List recent sessions from persistent memory, with optional limit and workspace filters, to access prior project context.

Instructions

List recent sessions.

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

Input Schema

NameRequiredDescriptionDefault
limitNoMax sessions to return
workspace_pathNoOptional: filter by workspace

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.2.0

TDQS

B3.1/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It only says 'recent sessions' without explaining ordering, whether active sessions are included, what fields are returned, or whether the operation is purely read-only. 'List' implies read-only, but the description does not elaborate on behavior beyond the name.

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 just three words and contains no redundancy or filler. It is front-loaded with the key action and object, and every word contributes to the meaning.

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

Completeness3/5

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

For a simple list tool with two optional, well-documented parameters, this is minimally viable. However, there is no output schema and no description of return values, sorting semantics, or what 'recent' means, so an agent still has some ambiguity about the exact behavior and response shape.

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 description coverage is 100%, so the schema already documents both parameters (limit and workspace_path). The description itself adds no parameter-level meaning, but baseline 3 is appropriate because the schema carries the semantic weight.

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 states a clear verb and resource: 'List recent sessions.' This distinguishes it from siblings like start_session, end_session, get_session, and get_active_session by virtue of the 'list' action, but it does not explicitly differentiate it from similar listing or search tools like search_history.

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

Usage Guidelines2/5

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

The description offers no guidance on when to use list_sessions versus alternatives such as get_active_session, get_session, or search_history. It does not state prerequisites, exclusions, or preferred scenarios, so an agent must infer the usage context from the tool name alone.

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

Deploy Server

Other Tools