List all active and recent opencode sessions.
List all active and recent opencode sessions.
{"success": bool, "message": str, "data": {"sessions": [{"id": str}]}}
opencode_list_sessions()
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections.
v0.2.11Output schema / (root)Previous value: -{
- "additionalProperties": true,
- "type": "object"
-}New value: +nullv0.2.3Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint and idempotentHint, so safety behavior is covered. The description adds a return format and an example, which is useful given there is no output schema, but it does not disclose auth requirements, rate limits, or what 'recent' means operationally.
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?
Purpose is front-loaded and the return format is compact. The example 'opencode_list_sessions()' adds little for a zero-argument tool, but overall length is appropriate.
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 zero-parameter, read-only listing tool with annotations and no output schema, the description supplies the missing return shape. The main remaining gap is sibling differentiation from opencode_sessions.
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 takes zero parameters, so the schema has nothing to document and the baseline is 4. The description correctly avoids burdening the reader with nonexistent parameter details.
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?
States the specific verb 'List' and resource 'opencode sessions' and adds the scope 'active and recent'. This helps distinguish it from a single-session getter, though it does not explicitly differentiate from the sibling opencode_sessions.
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?
Provides no explicit when-to-use guidance, no exclusions, and does not name alternatives such as opencode_sessions or opencode_get_session. The agent must infer selection from the purpose line alone.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.