Generate an image from a prompt via CLIProxy, save it locally, and return the absolute path, dimensions, and PNG preview.
通过 CLIProxy 的 images/generations 生成一张图片并保存本地，返回绝对路径、实际尺寸和 PNG 预览。默认 gpt-image-2.5-flare，也可指定 gpt-image-2.5-sunburst 或其他模型。可能消耗额度，失败不自动重试。
| Name | Required | Description | Default |
|---|---|---|---|
| size | No | 请求尺寸，例如 1024x1024、1536x1024；支持情况取决于模型，实际尺寸以结果为准 | |
| model | No | CLIProxy 模型 ID；省略时使用配置中的默认模型 | |
| prompt | Yes |
Changes observed during successful MCP inspections.
v0.2.2Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations only state not read-only, not idempotent, and not destructive. The description adds valuable context: it saves to local storage, may consume quota, and does not auto-retry on failure. This goes beyond annotation data without contradicting it.
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?
Two dense sentences: the first front-loads the core action and return values, the second covers model selection and important caveats about quota and retries. 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?
With no output schema, the description's mention of returned absolute path, actual dimensions, and PNG preview is essential and adequate. It also covers model default and failure behavior. Minor gaps remain, such as where the file is saved and overwrite behavior, but these are not critical for invoking the tool correctly.
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 67% and two parameters already have schema descriptions. The description adds the default model (gpt-image-2.5-flare) and allowed alternatives, which is useful beyond the schema. However, it does not add meaning for the prompt parameter beyond what the schema implies.
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?
Description states a specific verb and resource: generate an image via CLIProxy's images/generations endpoint, save it locally, and return absolute path, actual dimensions, and PNG preview. This clearly distinguishes it from sibling tools list_models and generate_text.
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 explicit when-to-use guidance or alternatives are mentioned. The description explains how the tool behaves (default model, quota, retry policy) but does not tell the agent when to choose this over generate_text or list_models.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.