Retrieve a list of active code interpreter sessions, optionally limiting the number returned. Use this to review or manage existing execution environments.
List all code interpreter sessions
| Name | Required | Description | Default |
|---|---|---|---|
| maxResults | No | Maximum number of sessions to return |
Changes observed during successful MCP inspections.
v1.0.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description carries the full disclosure burden. It clearly indicates a read-only listing operation and the scope ('all sessions'), but it does not mention ordering, which session states are included, whether results are paginated, or exactly what fields are returned. This is minimal but not misleading.
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?
The description is a single, front-loaded phrase with no filler or redundant information. Every word contributes to understanding the tool's function.
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 tool with zero required parameters and one optional parameter, the description is nearly sufficient. However, with no output schema and no annotation context, it leaves some ambiguity about the return format and the exact meaning of 'all sessions' (e.g., active, historical, or both).
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?
The only parameter, maxResults, is fully described in the schema, so schema coverage is 100%. The description adds no additional meaning about defaults, bounds, or how the limit is applied, which is acceptable given the schema already documents the parameter.
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 a precise resource ('all code interpreter sessions'), making the tool's purpose unambiguous. It is easily distinguished from siblings like get_session (single session) and start_session/stop_session (session lifecycle).
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?
Usage is implied by the name and description: use this tool when you need a list of all code interpreter sessions. However, there is no explicit guidance about when to prefer list_sessions over get_session, or whether this is appropriate before starting a session.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.