Skip to main content
Glama

Typebar (formerly SuperDocs)

list_sessions

Returns sessions sorted by most recent activity, with message counts and last-updated timestamps. Each session represents one document with full edit history and AI conversation persisted server-side. Use to find a previous editing context to resume (then call get_session_history) or to audit your workspace.

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
limitNoMaximum number of sessions to return
user_idNoFilter by user ID (deprecated - auth determines scope)

Output Schema

NameRequiredDescriptionDefault
totalYesTotal number of sessions returned.
sessionsYesArray of session summaries, ordered by most recent activity.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.9/5.0
Behavior5/5

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

With no annotations provided, the description bears the full burden of behavioral disclosure. It explains what is contained within each session (edit history, AI conversation, message counts), how it is sorted (most recent activity), and the operational constraint that user scope is determined by authorization, not just the `user_id` parameter.

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 definition is highly efficient. The first sentence describes the technical output and content, and the second sentence describes the logical use cases and necessary downstream tool interactions.

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 provides all necessary context, including what constitutes a 'session' and how this tool fits into the broader workflow (e.g., requiring a follow-up call to `get_session_history`). It is fully comprehensive.

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?

While the schema coverage is 100%, the description adds critical semantic value by labeling the `user_id` filter as 'deprecated' and clarifying that scope is determined by authorization, which is crucial context missing from the structured schema alone.

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 explicitly states that the tool returns sessions sorted by most recent activity, clearly defining the resource and its primary function. It is distinct from other session-related tools, specifying its role in listing sessions for auditing or context finding.

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 provides strong usage guidance by directing the agent on how to use the output: specifically, using the results to find a context to resume using `get_session_history`. It defines two clear use cases: resuming context or auditing workspaces.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.