opencode-mcp

opencode_session_list

Read-onlyIdempotent

List OpenCode sessions for a project to review active or past coding tasks. Provide an absolute directory path to filter sessions for a specific project.

Instructions

List all sessions

Input Schema

TableJSON Schema

Name	Required	Description	Default
`directory`	No	Absolute path to the project directory. When provided, the request targets that project. If omitted, the OpenCode server uses its own working directory.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`data`	No
`text`	Yes
`isError`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv3.0.0Sep 16, 2026

TDQS

B3.1/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, covering the safety profile. The description adds no extra behavioral context, such as what 'all sessions' means (global vs. project-scoped) or whether results are paginated. With annotations present, the bar is lower, but the description adds no value beyond the annotations.

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?

The description is a single, front-loaded sentence with no fluff. It is appropriately concise for the simplicity of the tool, though it could be slightly expanded to clarify scope without losing efficiency.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool has an output schema and multiple sibling tools that also deal with sessions, the description is too minimal. It fails to clarify whether 'all sessions' means all sessions across projects or only within the specified directory. This ambiguity could lead an agent to misuse the tool or select an inappropriate sibling.

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 description coverage is 100%, and the only parameter 'directory' is fully documented in the schema. The description does not add any extra meaning about the parameter, but since the schema carries the full burden, the baseline of 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states the verb 'List' and the resource 'sessions', making the core action clear. However, it does not differentiate from sibling tools like opencode_sessions_overview or opencode_session_search, which could also list sessions. It is not a tautology, but it lacks the specificity needed to distinguish it from similar operations.

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 is provided on when to use this tool versus alternatives. The description does not mention any conditions, exclusions, or alternative tools, leaving the agent to infer the appropriate usage context from the parameter schema alone.

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

Deploy Server