Zhenzhen Image MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_model_guideA | 免费本地模型选择建议和配置状态；只检查密钥是否存在，不显示密钥、不请求云端。 |
| generate_imageB | 同步生成并落盘。默认逆向五参数；官转须显式 group=official。收费，POST 不自动重试。 |
| edit_imageA | 同步图像编辑并落盘；多图以 image[] 上传。高编辑精度场景建议 Sunburst。收费。 |
| submit_image_generationA | 提交收费异步绘图并返回 task_id；服务存活时每90秒自动查询并落盘。可选 idempotency_key 防重。 |
| submit_image_editA | 提交收费异步编辑，以 image[] 上传；每90秒自动查询并落盘。可选 idempotency_key 防重。 |
| submit_image_batchA | 一次提交1–20项收费异步生成/编辑，默认并发5、最多20。收到编号即返回，后台每90秒查询并落盘。同一(checkpointer,thread_id,task_id)及参数复用，冲突拒绝；不确定提交永不自动重发。 |
| run_image_batchA | 同步执行1–20项收费生成/编辑，默认并发5，完成并校验落盘后返回。稳定三元组防重；重放验证文件SHA-256，不重复收费；超时/未知结果禁止重发。 |
| get_image_batchA | 免费读取本地持久化检查点，恢复该会话所有 task_id/provider_task_id/最后观察状态；不查询供应商、不提交、不等待成图。 |
| get_batch_image_taskA | 按原(checkpointer,thread_id,task_id)查询供应商异步结果并自动落盘；只读HTTP有限重试。没有供应商编号时返回本地状态，不重新提交。云端失败为工具错误；检查 result.save_status。 |
| get_image_taskA | 查询 NOT_START（排队）/IN_PROGRESS/FAILURE/SUCCESS；暂时性查询故障最多尝试3次。save=true 时成功图片自动落盘；false 仅查询。不重新提交。 |
| wait_image_taskA | 有界轮询，NOT_START 排队和 IN_PROGRESS 处理中继续等待，成功后落盘；只读查询有限重试计入等待时限。超时返回 task_id/wait_timed_out，云端任务继续；可稍后再次查询。 |
| download_imageA | 按图片 URL 下载并校验 PNG/JPEG/WebP，自动落盘返回绝对路径；不会附带供应商 API Key。 |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| image_workflow | 根据用户需求选择模型与同步/异步绘图流程；模板本身不收费。 |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| model_resource | Static model advice and compatibility statement; no secrets or cloud calls. |
TDQS
Scored across 12 tools
The set contains several near-pairs: generate_image vs submit_image_generation, edit_image vs submit_image_edit, submit_image_batch vs run_image_batch, and get_image_task vs get_batch_image_task vs get_image_batch. Descriptions clarify sync vs async and local vs provider state, but an agent can still easily misselect among similarly named tools.
All names are snake_case with verb-first structure, but the conventions vary between verb_resource_action (submit_image_batch), verb_resource (generate_image), and inconsistent ordering such as get_image_batch vs get_batch_image_task. The patterns are readable but not predictable enough to prevent confusion.
Twelve tools is a reasonable scope for covering sync/async generation, editing, batch execution, querying, waiting, and downloading. Some sync/async/batch variants feel redundant, but each mode can earn its place.
The surface covers generation, editing, batch operations, task polling, download validation, and model guidance. Minor gaps exist around cancellation or management of async jobs, but core image workflows are covered.