List available image generation models from OpenRouter with pricing and capabilities. Filter by substring on model ID or name.
List available image generation models from OpenRouter with pricing and capabilities.
| Name | Required | Description | Default |
|---|---|---|---|
| query | No | Filter models by substring match on model ID or name |
Changes observed during successful MCP inspections.
v0.1.1Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full burden. It states what is listed but not whether results are cached, how fresh pricing data is, whether authentication is required, or if the list is paginated.
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?
A single efficient sentence that front-loads the action and resource with no wasted words.
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?
Adequate for a simple read-only single-param tool, but with no annotations and no output schema, the description could reasonably say more about return shape or usage context.
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 coverage is 100%, with the query parameter fully documented as a substring match. The description adds no parameter details, so baseline 3 applies.
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?
Clear verb+resource: lists image generation models, and specifies source (OpenRouter) and included data (pricing, capabilities). It distinguishes itself from siblings like generate_image by being a read-only catalog operation, though it does not explicitly name them.
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?
No guidance on when to use this versus alternatives or prerequisites. An agent could infer it's for discovering models before calling generate_image, but nothing is stated explicitly.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.