List active and recently ended terminal sessions to track shell processes running on your machine. See what's executing or finished to manage ongoing work.
List active and recently completed persistent terminal sessions.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections.
v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds the detail about including 'recently completed' sessions, which is useful context beyond the annotations. However, it does not disclose what 'recently' means or any potential limits on the list size, though these are minor for a simple read-only list operation.
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 sentence with no wasted words. It is front-loaded with the action and resource, and completely appropriate for the tool's simplicity.
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?
The description is adequate for a basic list tool, but it does not specify the return format (e.g., whether it returns session IDs, names, or other metadata). Since there is no output schema, the agent must infer what the list contains to use the results with sibling tools. A brief mention of the returned fields would improve completeness.
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 tool has zero parameters, so the schema fully covers everything. According to the rubric, a baseline of 4 is appropriate for 0-parameter tools since nothing is needed to clarify parameter usage. The description correctly contains no parameter information.
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 clear verb ('List') and resource ('persistent terminal sessions'), and specifies the scope ('active and recently completed'). It distinguishes from siblings like lb_shell_output or lb_shell_kill, which operate on individual sessions rather than enumerate them.
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?
No explicit guidance is given about when to use this tool versus alternatives. While it's implied that this is the enumeration tool before using session-specific tools (lb_shell_output, lb_shell_input, etc.), the description does not state that or any usage context. This is a gap for an agent that needs to decide between multiple session-related tools.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.