Skip to main content
Glama

list_image_models

List which OpenAI image models your API key can access, ordered newest first, showing the default model and any pinned choice. Filter results with optional keywords.

Instructions

Lists the OpenAI image models the user's API key can use, newest first.

Shows which model is used by default and whether the user pinned one.

Args:
    query: Optional words to filter by, such as "2.5" or "flare".

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_image_models"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.2/5.0
Behavior4/5

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

With no annotations provided, the description carries the full load and does well: "Lists" signals a non-mutating read, "the user's API key can use" discloses that results are auth-scoped, "newest first" discloses ordering, and the return content (default model indicator, pinned indicator) is summarized. Remaining gaps are minor — no explicit statement of read-only safety, rate limits, or pagination behavior.

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 core purpose and ordering are front-loaded in one sentence, the returned information in the second, and the single parameter is documented compactly with examples. Nothing is redundant with the title or restates the schema.

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

Completeness4/5

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

For a one-optional-parameter read tool with an output schema (so return values need not be explained), the description covers purpose, scope, ordering, return highlights, and filter usage. Only matching semantics and any limits on result count are left unaddressed.

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

Parameters4/5

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

Schema coverage is 0%, so the description must compensate, and it does: it marks query as optional and gives concrete filter examples ("2.5", "flare") that clarify the intended kind of matching. It stops short of specifying matching semantics (substring vs. exact, case sensitivity).

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?

"Lists the OpenAI image models the user's API key can use, newest first" gives a specific verb (lists), a specific resource (image models), the scope (models the key can access), and the ordering. It is trivially distinguishable from the sibling mutation tools edit_image and generate_image.

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

Usage Guidelines3/5

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

Usage is implied rather than stated: an agent can infer this is the discovery call to make before generate_image, and the description notes it reveals the default and any pinned model. There is no explicit "use this when..." guidance, no exclusion of alternatives, and no mention of prerequisites beyond a valid API key.

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

Deploy Server

Other Tools