opencode-mcp

opencode_tool_list

Read-onlyIdempotent

Retrieve JSON schemas for tools available with a specified provider and model, targeting a project directory when needed.

Instructions

List tools with JSON schemas for a given provider and model (experimental)

Input Schema

TableJSON Schema

Name	Required	Description
`model`	Yes	Model ID
`provider`	Yes	Provider ID
`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

A4.1/5.0

Behavior3/5

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and non-destructive behavior, so the safety profile is covered. The description adds the 'experimental' flag, which is useful context, but does not disclose further behavioral details such as pagination, errors, or format specifics.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, front-loaded sentence with no wasted words. It conveys the core action, resource, scoping, and an experimental caveat efficiently.

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

Completeness5/5

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

The combination of a complete parameter schema, rich annotations, and an output schema covers the operational details. The description adds the key semantic information—listing tools with JSON schemas for a provider/model—so nothing essential is missing for an agent to invoke it correctly.

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%, so the input schema already documents all three parameters. The description restates provider and model contextually but adds no additional meaning beyond the schema, so the baseline score of 3 is appropriate.

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

Purpose5/5

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

The description uses a specific verb ('List') and a distinct resource ('tools with JSON schemas'), scoped by provider and model. This makes it easy to distinguish from siblings like opencode_tool_ids or opencode_provider_models without needing to inspect them.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description clearly indicates when to use this tool: when tool schemas are needed for a given provider and model. It does not mention alternatives or exclusions, but the context is sufficiently clear for selection among siblings.

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

Deploy Server