Opens the TUI model selector in OpenCode, enabling quick model switching for a specified project directory directly from the terminal.
Open the model selector in the TUI.
| Name | Required | Description | Default |
|---|---|---|---|
| directory | No | Project directory to target. Optional; defaults to the server default project. |
Changes observed during successful MCP inspections.
v3.0.0Does 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 says only that the selector opens in the TUI; it does not disclose side effects, whether it changes server state, permission requirements, or what happens after the selector opens.
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 sentence with no wasted words. It is appropriately sized for a simple TUI-opening action.
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 parameterless UI action, the description and schema together are minimally adequate. However, with no annotations and no output schema, it omits any behavioral or usage context that could help an agent decide whether to invoke it.
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% for the single optional directory parameter, so the schema already explains it adequately. The description adds no parameter-level details, which is acceptable given the high coverage 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 (Open) and resource (model selector) and explicitly scopes it to the TUI, distinguishing it from sibling UI tools like open_help, open_sessions, and open_themes. An agent can identify the action without opening the schema.
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 indication of when to use this tool versus alternatives such as opencode_provider_models or other model-related tools. No conditions, prerequisites, or exclusions are provided.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.