opencode-image-mcp

List image models

list_models

Read-onlyIdempotent

Discover image-capable models from configured providers, querying endpoints and caching results. Use refresh to bypass cache or filter by provider.

Instructions

Discover image-capable models offered by configured providers.

Queries each provider's model endpoint, filters to image models, and caches the result on disk. Set refresh=true to bypass the cache. Pass provider to query just one provider.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`refresh`	No
`provider`	No

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Sep 26, 2026

TDQS

A4.6/5.0

Behavior4/5

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

The description adds behavior beyond annotations: it queries each provider's endpoint, filters to image models, and caches on disk. It also explains the refresh parameter as cache bypass. Annotations already cover read-only and idempotent safety, so the added detail is valuable and non-contradictory.

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?

Three sentences with no fluff. The purpose is front-loaded, and behavioral/parameter details follow efficiently. Every sentence earns its place.

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?

Given the presence of an output schema (which covers return values) and read-only annotations, the description fully explains what the tool does, how it behaves (caching, filtering), and how to control it via parameters. Nothing essential is missing for safe invocation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must fully explain parameters. It does: 'refresh' is defined as bypassing the cache, and 'provider' as limiting to one provider. This adds meaning beyond the bare type/default schema.

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 states a specific action ('Discover image-capable models') with a clear resource ('offered by configured providers') and distinguishes it from siblings like list_providers and generate_image. It leaves no ambiguity about what the tool does.

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?

Provides clear context on when to use (discover available image models) and how to adjust behavior via 'refresh' and 'provider'. It does not explicitly name alternatives or exclusion cases, but the purpose is self-evident in the sibling context, so this meets the 'clear context, no exclusions' level.

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

Deploy Server