Zhenzhen Image MCP

submit_image_generation

Submits paid asynchronous image generation jobs, returns a task_id, and auto-polls every 90 seconds to save results to disk. Optional idempotency keys prevent duplicate charged requests.

Instructions

提交收费异步绘图并返回 task_id；服务存活时每90秒自动查询并落盘。可选 idempotency_key 防重。

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "prompt": "<prompt>",
      "model": "<model>"
    },
    "name": "submit_image_generation"
  }
}

Input Schema

Name	Required	Description	Default
`size`	No	可选 auto 或 WIDTHxHEIGHT；两边为16倍数、最大3840、比例不超过3:1、总像素655360..8294400。省略时不发送。
`group`	No	分组声明：默认 reverse（逆向）；仅用户明确使用官转时传 official。此字段不发送上游、不改变密钥后台分组。	reverse
`model`	Yes	GPT Image 2.5 Sunburst 非常适合对编辑精度要求极高的应用场景；GPT Image 2.5 Flare 是目前用于生成高质量图片的最快模型。模型可以接受文本和图片作为输入，然后输出相应的图片。以上为用户提供的供应商选型说明，尚未做速度或质量对比实测。请结合用户意图选择并告知所用模型。
`images`	No
`prompt`	Yes
`quality`	No
`output_dir`	No	可选绝对输出目录；默认配置目录。异步任务查询默认沿用提交目录。
`idempotency_key`	No	可选稳定幂等键；相同参数复用，参数改变拒绝，禁止换键重试未知收费结果。
`official_options`	No	仅 group="official" 可用的官转扩展参数。未声明官转时传入此对象会在收费前拒绝。

Output Schema

Name	Required	Description	Default
`cost`	No
`note`	No
`files`	No
`group`	No
`usage`	No
`reused`	No
`status`	Yes
`task_id`	No
`warning`	No
`progress`	No
`response`	No
`next_tool`	No
`output_dir`	No
`fail_reason`	No
`save_status`	No
`wait_timed_out`	No
`download_errors`	No
`idempotency_key`	No
`auto_poll_interval`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedv0.4.0Oct 23, 2026

addedInput schema / properties / idempotency_key

Added value: +{
+  "anyOf": [
+    {
+      "pattern": "^[A-Za-z0-9_-]{1,128}$",
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "可选稳定幂等键；相同参数复用，参数改变拒绝，禁止换键重试未知收费结果。",
+  "title": "Idempotency Key"
+}

addedOutput schema / properties / auto_poll_interval

Added value: +{
+  "title": "Auto Poll Interval",
+  "type": "integer"
+}

addedOutput schema / properties / idempotency_key

Added value: +{
+  "title": "Idempotency Key",
+  "type": "string"
+}

addedOutput schema / properties / reused

Added value: +{
+  "title": "Reused",
+  "type": "boolean"
+}

First observedv0.3.0Oct 20, 2026

TDQS

A3.6/5.0

Behavior4/5

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

Beyond the annotations (readOnlyHint=false, openWorldHint=true), the description discloses the important behaviors: the call is billed ('收费'), it is asynchronous and only returns a task_id, the tool auto-polls every 90 seconds while the service is up and persists results to disk, and an optional idempotency_key dedupes submissions. That is material context an agent would not get from the annotation block alone. The mild tension between 'idempotentHint: false' and the idempotency_key option is resolved by the schema's explanation of stable-key semantics, so it is not a contradiction.

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

Conciseness4/5

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

Two short clauses, front-loaded with the verb and the returned handle, then the lifecycle and dedupe notes. Every clause carries information, though the compressed phrasing ('落盘') is slightly opaque for an agent parsing intent.

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

Completeness3/5

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

The description covers the cost, async lifecycle, polling/persistence, and idempotency, and an output schema covers return values, which is adequate for a 9-parameter paid tool. It still leaves the follow-up retrieval story (get_image_task / wait_image_task) and the relationship to the batch siblings unstated.

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 67% across 9 parameters, so much of the parameter meaning is already in structured fields (model selection text, size constraints, idempotency_key rules). The description only reinforces idempotency_key's anti-duplicate purpose and says nothing about images, official_options, output_dir, or group; an output schema exists, so return-value explanation is rightly omitted, keeping this at the baseline 3.

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

Purpose4/5

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

The description gives a specific verb+resource ('提交收费异步绘图') and names the immediate return value (task_id), so an agent can tell this is an async submission rather than a synchronous generation or edit. It does not explicitly name the sibling it is not (generate_image, submit_image_edit, submit_image_batch), so sibling differentiation is left to inference.

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?

The async nature ('异步' + returns task_id) implies this is the submit-then-poll path, and the idempotency_key mention hints at retry safety, but the description never states when to pick this over generate_image, submit_image_edit, or submit_image_batch, nor any when-not conditions.

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

Deploy Server