Open Notebook MCP Server

list_chat_sessions

Retrieve chat sessions with optional filtering by notebook ID and limit results. Access a list of sessions and metadata for your notebooks.

Instructions

Get all chat sessions with optional filtering.

Args:
    notebook_id: Optional notebook ID to filter by
    limit: Maximum number of results (1-100)

Returns:
    Dictionary with sessions list and metadata

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_chat_sessions"
  }
}

Input Schema

Name	Required	Description	Default
`notebook_id`	No
`limit`	No

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.2.0Jun 10, 2026

TDQS

B3.2/5.0

Behavior2/5

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

No annotations provided, so description carries full burden. It fails to disclose behavioral traits such as authentication requirements, rate limits, pagination behavior beyond the limit parameter, or default ordering of results.

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?

Description is short and front-loaded with main action. The Args section is somewhat redundant with schema but includes return info. No unnecessary sentences.

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?

Given simple list function with 2 optional parameters and an output schema, the description adequately covers purpose and basic filtering. However, it lacks details about output structure (though schema provides it) and fails to mention any metadata returned.

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 coverage is 0%, but description adds meaning: 'notebook_id' is explained as filter criterion, and 'limit' is given a range (1-100) not in schema. However, it does not explain that these parameters are optional or provide default behavior contexts.

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?

Description clearly states 'Get all chat sessions with optional filtering', which is a specific verb-resource pair. It distinguishes from siblings like 'get_chat_session' (single) and 'create_chat_session'.

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?

No guidance on when to use this tool versus alternatives like 'get_chat_session' for individual sessions or 'search' for broader queries. Lacks explicit context for selection.

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