list_sessionsBrowse available thinking sessions and return their metadata, with limit and offset controls to paginate through stored reasoning sessions.
List all available thinking sessions with metadata.
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | Maximum number of sessions to return | |
| offset | No | Pagination offset |
Changes observed during successful MCP inspections.
v1.3.1Does 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 does not state result ordering, whether the list is paginated (the schema's limit/offset imply it, but the description never mentions it), or what "metadata" concretely contains.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
A single front-loaded sentence with no filler or redundancy. It is efficient, though the efficiency comes partly from omitting useful information rather than from tight editing of richer content.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a simple two-parameter list tool with a 100%-covered schema and no output schema, the description is minimally sufficient. Still, the content of "metadata" and the pagination/default behavior are left entirely to the schema, so the agent must infer the shape of results.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100%, so both limit and offset are fully documented in the schema with defaults and bounds. The description adds nothing beyond that, which is acceptable but no better than the baseline.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description states a specific verb ("List") and resource ("thinking sessions") and notes that metadata is included, so an agent knows what it retrieves. However, it does nothing to distinguish itself from siblings like search_all_sessions or get_session_info, leaving the agent to infer the difference.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
There is no guidance on when to use this versus search_all_sessions, search_in_session, or get_session_info. The word "all" hints at an unfiltered enumeration, but no condition, exclusion, or alternative is named.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.